On 2013-03-18 12:39 PM, L. David Baron wrote:
I'd actually like to see Core higher on the list for the no-canconfirm case. I think it's common for reasonably well-informed Web developers (who would have been able to choose a reasonably correct component within Core, given the list) to file standards bugs and end up with them languishing in Firefox::General. And I think appropriate guiding for Web developers filing bugs against the rendering engine is an important case.
I agree with all of this, but I think that even very well-informed Web developers might find the Core component list daunting and incomprehensible. I think it'd be a good idea to have a special bug-entry wizard just for "Firefox didn't render this page correctly" that knows how to map standard web development terminology (HTML, JavaScript, CSS, tables, forms, accessibility, ...) to components, and which also encourages inclusion of things like self-contained minimal test cases, screen shots, and cross-browser comparisons.
zw _______________________________________________ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform
