Issue metadata
Sign in to add a comment
|
Need clear bug policy on handling of interop issues |
||||||||||||||||||
Issue descriptionWhat is the appropriate use of chromium bugs in regards to interop issues? Whose responsibility is it when chromium implements behavior that doesn't match a spec? To what extent is it a chromium bug when the spec is un-tested or otherwise ambiguous? We've debated these questions at some length and have established common conventions within specific teams, but don't yet have a clear policy for the chromium project. I'm working on fixing this.
,
Oct 23 2017
FWIW here are some sample Chromium issues (assigned to me) that are mostly about interop: crbug.com/698559, crbug.com/729137, crbug.com/692832. Not sure if you want to record this as "blocking" them, but I thought it'd be useful to have some samples.
,
Oct 23 2017
,
Oct 23 2017
,
Oct 23 2017
domenic: Yeah having examples that would be influenced by this policy are useful. Issue 549211 is another good long-time example IMHO. If you feel progress isn't likely until this is resolved, then indeed feel free to block on this.
,
Oct 24 2017
Hotlist:Interop https://bugs.chromium.org/p/chromium/issues/list?can=2&q=hotlist%3Ainterop has 1170 bugs on it. The Style and Animations team defines that a bug should be on Hotlist:Interop as "Compatibility bugs (differences in behaviour between Blink and other engines, or between Blink and a CR specification)"
,
Oct 31 2017
The NextAction date has arrived: 2017-10-31
,
Mar 21 2018
Any status update here? |
|||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||
Comment 1 by rbyers@chromium.org
, Oct 23 2017