Closed
Bug 573387
Opened 14 years ago
Closed 14 years ago
For SVG overflow='auto' should work like overflow='visible'
Categories
(Core :: SVG, defect)
Core
SVG
Tracking
()
RESOLVED
WONTFIX
Tracking | Status | |
---|---|---|
status2.0 | --- | wanted |
People
(Reporter: longsonr, Unassigned)
References
Details
Attachments
(1 file)
9.83 KB,
patch
|
Details | Diff | Splinter Review |
http://www.w3.org/TR/SVG/masking.html#OverflowProperty (4th bullet) and http://dev.w3.org/SVG/profiles/1.1F2/test/harness/htmlObject/painting-marker-05-f.html
Reporter | ||
Comment 1•14 years ago
|
||
Assignee: nobody → longsonr
Attachment #452600 -
Flags: review?(dbaron)
Attachment #452600 -
Flags: feedback?(jwatt)
Comment 2•14 years ago
|
||
Do we already have tests for svg, symbol, pattern and foreignObject? If not, can you rename the test to something like 'overflow-01.svg' and test each of those in its own little section of the screen?
I think this is a bad idea, since it gets along really badly with the overflow-x/overflow-y split.
Comment 4•14 years ago
|
||
David sent an email about this to www-svg: http://lists.w3.org/Archives/Public/www-svg/2010Jul/0000.html
David's perfectly right. We should treat 'auto' as 'hidden'.
Reporter | ||
Comment 7•14 years ago
|
||
OK then.
Status: NEW → RESOLVED
Closed: 14 years ago
Resolution: --- → WONTFIX
Reporter | ||
Updated•14 years ago
|
Attachment #452600 -
Flags: review?(dbaron)
Attachment #452600 -
Flags: feedback?(jwatt)
Comment 9•14 years ago
|
||
Goodness, my Bugzilla search-fu for existing bugs is weak. :-) I'm sad to say that David's mail never got a reply, nor did it become a tracked issue. I will bring it up again.
Reporter | ||
Updated•7 years ago
|
Assignee: longsonr → nobody
Reporter | ||
Comment 11•7 years ago
|
||
(In reply to Cameron McCormack (:heycam) from comment #9) > Goodness, my Bugzilla search-fu for existing bugs is weak. :-) > > I'm sad to say that David's mail never got a reply, nor did it become a > tracked issue. I will bring it up again. Raised https://github.com/w3c/svgwg/issues/329
You need to log in
before you can comment on or make changes to this bug.
Description
•