Re: [webkit-dev] Proposed changes to Bugzilla 'Resolution' categories

> 10 февр. 2022 г., в 12:06 PM, Michael Catanzaro via webkit-dev > написал(а): > > On Thu, Feb 10 2022 at 11:55:56 AM -0800, Brent Fulgham via webkit-dev > wrote: >> (1) Add a new “Behaves As Designed” option: >>> This will represent bugs that were filed when the reporter misunderstands a

Re: [webkit-dev] Proposed changes to Bugzilla 'Resolution' categories

On Thu, Feb 10 2022 at 11:55:56 AM -0800, Brent Fulgham via webkit-dev wrote: (1) Add a new “Behaves As Designed” option: This will represent bugs that were filed when the reporter misunderstands a feature, or wants behavior that we have considered, but chosen not to allow. This would be

Re: [webkit-dev] Proposed changes to Bugzilla 'Resolution' categories

Hi! Pretty sure WORKSFORME corresponds to “Behaves As Designed”, that’s how Mozilla’s bugzilla’s instance uses it at least. Adding new resolution statuses seems fine, but maybe old ones (WORKSFORME, WONTFIX, INVALID, etc.) should be cleaned up/migrated too, otherwise folks (coming from other

[webkit-dev] Proposed changes to Bugzilla 'Resolution' categories

Hi Floks, I would like to propose some changes to the categories we use to resolve bugs. I’ve been trying to do some Bugzilla gardening to better reflect the state of various “edge case” bugs that often leave users confused about the state of issues they’ve reported, and unsure of whether

Re: [webkit-dev] Proposed changes to Bugzilla 'Resolution' categories

Note we do have documentation of what they mean at https://webkit.org/bug-life-cycle/ , though this already appears to be incomplete (e.g., we have "CONFIGURATION CHANGED”, which I don’t know how people are meant to know what that means… what

Re: [webkit-dev] Proposed changes to Bugzilla 'Resolution' categories

> On Feb 10, 2022, at 11:55 AM, Brent Fulgham via webkit-dev > wrote: > > Hi Floks, > > I would like to propose some changes to the categories we use to resolve > bugs. I’ve been trying to do some Bugzilla gardening to better reflect the > state of various “edge case” bugs that often leave

[webkit-dev] Request for position: prerendering

Hi webkit-dev, This is a request for WebKit’s position on prerendering, which Safari already ships. Chrome would like to ship the feature too, and would like to do so in an interoperable way. We opened an issue at https://github.com/whatwg/html/issues/7533 , and have a draft spec at