L. David Baron wrote: > At today's Houdini task force meeting: > https://wiki.css-houdini.org/planning/paris-2015 some of the blink folks > (mainly Ojan Vafai) presented the outline of a proposal for > standardizing some aspects of the rendering pipeline / refresh cycle: > https://docs.google.com/document/d/1Mw6qNw8UAEfW96CXaXRVYPPZjqQS3YdK7v57wFttAhs/edit > which would probably replace at least parts of this bit of HTML: > https://html.spec.whatwg.org/multipage/webappapis.html#processing-model-9 > > My initial sense is that it seems reasonable to standardize, and we > should work out the details. Certainly from the standpoint of documenting layout for Web developers, it would be helpful if they knew painting and rendering would work the same way regardless of which browser the user chose to view the content in.
I've been thinking lately that a lot of things like this, where changes that might affect compatibility are being considered, might benefit from being released in tandem with the new add-on SDK. While at first it might seem unrelated, it really is. We're preparing to move our add-on community over to building add-ons that are strictly Web-tech based. This is a lot of change for them to go through, so it might make sense to carefully consider merging as many potentially breaking changes together as possible so we don't jerk them around too much. I don't know how much impact this particular change will have on add-on developers, but I've seen a few suggested browser-compatibility proposals that might affect existing code, so I thought I'd bring it up. Stretching out breaking changes over time just makes the pain last longer. :) -- Eric Shepherd Senior Technical Writer Mozilla <https://www.mozilla.org/> Blog: http://www.bitstampede.com/ Twitter: http://twitter.com/sheppy Check my Availability <https://freebusy.io/[email protected]> _______________________________________________ dev-tech-layout mailing list [email protected] https://lists.mozilla.org/listinfo/dev-tech-layout
