New issue
Advanced search Search tips

Issue 722376 link

Starred by 3 users

Issue metadata

Status: WontFix
Owner: ----
Closed: May 2018
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Compat



Sign in to add a comment

SVG's title tag that contains valid html is rendered correctly as tooltip only on the first svg element

Reported by ivan.g.h...@gmail.com, May 15 2017

Issue description

UserAgent: Mozilla/5.0 (Windows NT 10.0; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/57.0.2987.98 Safari/537.36 OPR/44.0.2510.857

Example URL:
https://jsfiddle.net/ihristov/phsk6bbt/1/

Steps to reproduce the problem:
1. Open the above jsfiddle
2. 
3. 

What is the expected behavior?
all the svg elements should display the tooltip the same way.

What went wrong?
the first (in creation order) svg element displays it correctly, but the others display the <title> contents as text instead of rendering it like a valid html.

Does it occur on multiple sites: N/A

Is it a problem with a plugin? No 

Did this work before? N/A 

Does this work in other browsers? Yes

Chrome version: 58.0.3029.110  Channel: stable
OS Version: 10.0
Flash Version: 

Works as expected in IE 11, Edge, Firefox
 
Components: Blink>SVG
Labels: Needs-Triage-M58
Labels: -Needs-Triage-M58 BugSource-User PaintTeamTriaged-20170515
Status: Available (was: Unconfirmed)
MDN's description of the element says this: "Each container element or graphics element in an SVG drawing can supply a <title> element containing a description string where the description is text-only." I interpret that to mean we can do whatever we want with content that isn't plain text.

Still, it's odd that we match other browsers on the first title but not the others. So leaving this open, but not a high priority.

Comment 3 by f...@opera.com, May 15 2017

Components: Blink>HTML>Parser
Labels: -OS-Windows
Inspecting this in DevTools this looks like a HTML parser bug - the first <title> has a proper descendant DOM, while numbers two to four just have a single text node.
Given that <title> is a bit special in this regard (it's an "HTML integration point") I suspect the insertion mode in the HTML parser is messed up at some point.

Comment 4 by f...@opera.com, May 15 2017

Parsing the same fragment via innerHTML gives the expected result, which indicates a bug in HTMLTreeBuilderSimulator.
Project Member

Comment 5 by sheriffbot@chromium.org, May 16 2018

Labels: Hotlist-Recharge-Cold
Status: Untriaged (was: Available)
This issue has been Available for over a year. If it's no longer important or seems unlikely to be fixed, please consider closing it out. If it is important, please re-triage the issue.

Sorry for the inconvenience if the bug really should have been left as Available.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot

Comment 6 by f...@opera.com, May 16 2018

Status: WontFix (was: Untriaged)
Was fixed by/as part of  issue 805924 .

Sign in to add a comment