Bug 46460

Summary:

Text under nested link dropped

Product:

WebKit

Reporter:

Michael O'Rourke <mkorourk>

Component:

SVG

Assignee:

Nobody <webkit-unassigned>

Status:

RESOLVED FIXED

Severity:

Normal

CC:

mdelaney7, rwlbuis, zimmermann

Priority:

Version:

528+ (Nightly build)

Hardware:

OS:

Windows 7

Attachments:

Description	Flags
Example SVG file with text and links	none
Simplified example file	none
First attempt	krit: review+

Michael O'Rourke

Reported 2010-09-24 06:44:07 PDT

The text '5google.com', '6google.com, '7google.com' under a tspan are dropped from the display. This works fine in both Firefox 3.6.3 and IE 8.0.7600.16385 and the SVG content seems to be legal. This was seen in Chrome 6.0.472.63.

Attachments
Example SVG file with text and links (28.67 KB, image/svg+xml) 2010-09-24 06:44 PDT, Michael O'Rourke	no flags	Details
Simplified example file (603 bytes, image/svg+xml) 2010-09-24 07:02 PDT, Michael O'Rourke	no flags	Details
First attempt (80.83 KB, patch) 2010-10-16 12:22 PDT, Rob Buis	krit: review+	Details Formatted Diff Diff
View All Add attachment proposed patch, testcase, etc.

Michael O'Rourke

Comment 1 2010-09-24 06:44:49 PDT

Created attachment 68671 [details] Example SVG file with text and links

Michael O'Rourke

Comment 2 2010-09-24 07:02:10 PDT

Created attachment 68675 [details] Simplified example file

Michael O'Rourke

Comment 3 2010-09-24 07:03:49 PDT

I've attached a simplified example file with only one text span. If the <a> tag is removed then the text displays fine in webkit browsers. Note that the existing content still displays fine in IE and Firefox.

Rob Buis

Comment 4 2010-10-16 12:22:47 PDT

Created attachment 70961 [details] First attempt

Dirk Schulze

Comment 5 2010-10-16 23:49:03 PDT

Comment on attachment 70961 [details] First attempt r=me, but please move every case in a new line: || child->hasTagName(SVGNames::trefTag) || child->hasTagName(SVGNames::tspanTag) ...

Rob Buis

Comment 6 2010-10-17 23:52:07 PDT

Landed in r69922.

Note You need to log in before you can comment on or make changes to this bug.