New issue
Advanced search Search tips

Issue 744598 link

Starred by 1 user

Issue metadata

Status: WontFix
Owner: ----
Closed: Jul 2017
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 3
Type: Feature



Sign in to add a comment

SVG: Implement "marker" presentation attribute

Reported by paul.leb...@gmail.com, Jul 17 2017

Issue description

UserAgent: Mozilla/5.0 (Windows NT 6.1; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/59.0.3071.115 Safari/537.36

Steps to reproduce the problem:
Run test suite file: "painting-marker-04-f"

https://dev.w3.org/SVG/profiles/1.1F2/test/harness/htmlObject/painting-marker-04-f.html

What is the expected behavior?
Markers visible on the top shape.

What went wrong?
No markers.  It does work though if you use a "style" attribute of CSS.

    style="marker: url(#m);"

Did this work before? N/A 

Does this work in other browsers? N/A

Chrome version: 59.0.3071.115  Channel: stable
OS Version: 6.1 (Windows 7, Windows Server 2008 R2)
Flash Version: 

The "marker" presentation attribute has been in all versions of the SVG 1.1 spec, including the first.  

However it seems the "marker" attribute was accidentally(?) left out of the new "Presentation Attributes" section of the June 2010 edition (see https://www.w3.org/TR/2010/WD-SVG11-20100622/attindex.html#PresentationAttributes). This error was remedied a couple of versions later (see https://www.w3.org/TR/2011/PR-SVG11-20110609/propidx.html).  Perhaps that was the reason it was never implemented in Webkit?

However the attribute has been retained in SVG 2, so perhaps it is time to fix this omission?
 

Comment 1 by f...@opera.com, Jul 17 2017

Labels: -OS-Windows -Type-Bug -Pri-2 Pri-3 Type-Feature
Status: Available (was: Unconfirmed)
AFAIK, "marker" has never been in any version of the spec (at least 1.1+, 1.0 I've barely looked at...) as a _presentation_attribute_ [1] - it has been there as a property though.

I did dig through the archives a bit and found that this had been discussed (and resolved) five years ago [2]. Seems this never made it to the spec proper though. (The minutes touches upon what was considered to be a problem with doing this in the first place, I think.)

I think we'd at least want this be properly specced before we consider implementing it.

[1] https://www.w3.org/TR/2011/PR-SVG11-20110609/propidx.html is a property index - not a list presentation attributes (propidx != attindex).
[2] https://www.w3.org/2012/01/12-svg-minutes.html#item03
Sorry. You are right. I seem to have got confused somehow.  And I didn't properly read the info under the test suite item either :(

I notice that it *is* listed in SVG 1.0 as a property: https://www.w3.org/TR/2001/REC-SVG-20010904/propidx.html

I'll file a spec bug to try and get if people still think it should be specced. I'll leave it up to you whether to keep this bug open or not.
Actually "marker" is listed as a property (as is "font") in the SVG 2 spec:

https://svgwg.org/svg2-draft/single-page.html#chapter-propidx

Arrgh, bad day. Wish this site had a delete comment button when you make embarrassing mistakes... :/

Anyway, I've filed a spec bug to see if this issue can get resolved.

https://github.com/w3c/svgwg/issues/334

Comment 5 by f...@opera.com, Jul 17 2017

Status: WontFix (was: Available)
Yes, "font" would be in the same boat as "marker" - a property that does not have a presentation attribute. (BTW, https://svgwg.org/svg2-draft/single-page.html#attindex-PresentationAttributes is the list of presentation attributes - and being a property does not imply having a presentation attribute [although it is commonly so...]. I see you remembered that too - there is a "Delete comment", but I suspect it may only be available to people with "edit" permissions...)

Since we cannot hope to see any speedy spec-turnaround here, I might as well WontFix this issue, but we can reopen if so (given that someone remembers that this issue exists that is =))

Sign in to add a comment