Summary: | Safari incorrectly accepts "end safe" and incorrectly serializes "safe end" as "end safe" on various properties | ||
---|---|---|---|
Product: | WebKit | Reporter: | Eric Willigers <ericwilligers> |
Component: | CSS | Assignee: | Nobody <webkit-unassigned> |
Status: | RESOLVED FIXED | ||
Severity: | Normal | CC: | jfernandez, simon.fraser, webkit-bug-importer, zalan |
Priority: | P2 | Keywords: | FromImplementor, InRadar |
Version: | Safari 11 | ||
Hardware: | Unspecified | ||
OS: | Unspecified |
Description
Eric Willigers
2018-09-13 04:51:15 PDT
I can take a look at this issue, if nobody is currently working on it. I cannot reproduce the issue in my current trunk (r233461). The commit landed in r227432 should precisely implement the expected behavior, so that <overflow-position> is parsed as invalid if it doesn't precede a either a <content-position> or <self-position> keyword. As a matter of fact, the mentioned patch provides tests to verify that "start safe" and "end unsafe" are parsed as invalid: https://trac.webkit.org/browser/webkit/trunk/LayoutTests/css3/parse-align-self.html#L227 Maybe the patch in r227432 has not been merged into the Safari version the issue was reported for ? > I cannot reproduce the issue in my current trunk (r233461).
I was testing with Safari 11.1 (using browserstack.com)
I confirm this bug no longer occurs in Safari 12 (which browserstack.com now has)
|