[Webkit-unassigned] [Bug 189582] Safari incorrectly accepts "end safe" and incorrectly serializes "safe end" as "end safe" on various properties

bugzilla-daemon at webkit.org bugzilla-daemon at webkit.org
Mon Sep 17 02:54:44 PDT 2018


--- Comment #2 from Javier Fernandez <jfernandez at igalia.com> ---
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:


Maybe the patch in r227432 has not been merged into the Safari version the issue was reported for ?

You are receiving this mail because:
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.webkit.org/pipermail/webkit-unassigned/attachments/20180917/963f3fdc/attachment-0001.html>

More information about the webkit-unassigned mailing list