Hi Platform Team: I've asked Cameron McCormack to look into how Firefox and other browsers should behave when under mild to severe stress. As all browser engines have to manage how to run under low memory, feeble network, pegged CPU, weak GPU, low battery, small/slow screens, etc., I think web authors should know what to expect when their content is run on high-end machines and wristwatches. The hypothesis is that web authors will be frustrated by multiple browsers modifying their content for performance reasons without consistent/documented fallback scenarios. Cameron is initially focused on Web Rendering but we may want to specify what happens in other parts of the Platform as well, including the conditions that will trigger the graceful degradation of content.
Some features that may have value as normative specs for all browsers: reduced or no antialiasing reduced color depth image downsampling image resizing/culling animation throttling (frame-rate reduction or frame dropping) reduced font/text feature usage audio/video bit-rate throttling content purging (how?) definition of browser stress levels (device profiles?) My hope is that we can get the other browser engines to get behind these proposals, and that the "like Gecko" user agent designation also indicates adherence to these documented behaviors. Please reply to this thread, or to Cameron directly, with your thoughts/ideas on the topic. Thanks, --Jet _______________________________________________ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform
