A user account is required in order to edit this wiki, but we've had to disable public user registrations due to spam.
To request an account, ask an autoconfirmed user on Chat (such as one of these permanent autoconfirmed members).
Search results
Jump to navigation
Jump to search
- * Works for HTML without markup changes. ...IL (i.e. why is it considered the inferior choice)? ''SMIL requires markup changes to use, for stylistic effects''1 KB (229 words) - 10:05, 31 May 2012
- ** Time-based triggering ✓ ''(using script to trigger changes)'' ** Event-based triggering ✓ ''(using script to trigger changes)''6 KB (897 words) - 12:12, 26 January 2011
- | Changes the attribute name to lowercase. * TODO (need to talk about the changes to the DOM API that HTML5 is making, compared with DOM2 and DOM3)33 KB (5,299 words) - 12:41, 21 August 2011
- Parsing changes in this solution could be hard to implement given <caption> element's le Parsing changes in this solution could be hard to implement given <caption> element's legac8 KB (1,364 words) - 20:16, 10 October 2011
- ...s means that a binding should be able to detect and react to the following changes in DOM: ...hen the node is distributed to an insertion point by a rule, then the rule changes or is invalidated by a subtree mutation, the node remains in its position,6 KB (908 words) - 22:39, 28 July 2011
- ...s made by the WHATWG into their fork of the document (which also has other changes). Also in December 2017, [https://blog.whatwg.org/working-mode-changes the WHATWG gained a patent policy]:22 KB (3,546 words) - 08:47, 25 June 2019
- ...by the decorator. All of these constraints stem from the need to halt DOM changes in a decorator shadow subtree and include not allowing:3 KB (485 words) - 23:06, 22 November 2011
- To simplify the platform Acid3 needs various changes to its tests:949 bytes (145 words) - 09:25, 9 September 2011
- '''PRO 2:''' More changes are batched.6 KB (925 words) - 15:21, 16 August 2011
- ...ng a field's <code>name</code> requires coordinated front-end and back-end changes. Even for new websites, the <code>name</code> attribute might have back-en24 KB (3,732 words) - 19:47, 27 September 2014
- * Content changes couldn't be efficiently reflected in layout by doing partial updates if the3 KB (532 words) - 10:06, 5 June 2012
- .... But since it’s very common to quickly flip forward through short trivial changes, it’s best to not prerender previous until the prerender for next is quit4 KB (604 words) - 22:13, 7 November 2012
- ...extraction needs to be synchronous either because the source image content changes over time (e.g a canvas or video), or because the subrectangle coordinates6 KB (977 words) - 23:42, 6 September 2013
- '''Q:''' Why get rid of a commit method in workers to propagate changes from a context rendered in a worker to a canvas in the main page?19 KB (2,852 words) - 20:34, 18 August 2016
- ...ncrypted Media Extensions] W3C specification, and may well offer suggested changes to the EME specification that mitigate concerns raised. This is very much2 KB (323 words) - 21:23, 28 February 2013
- :''Explanation of the changes introduced by this solution. It explains how the document is processed, and7 KB (1,068 words) - 15:09, 21 April 2015
- This document proposes two behavioral changes for sandboxed <code><iframe></code> elements, each governed by a new5 KB (697 words) - 06:47, 16 July 2015
- :''Explanation of the changes introduced by this solution. It explains how the document is processed, and2 KB (240 words) - 12:12, 26 January 2011
- * Unicorn-compatible (hoping that Unicorn changes instead)9 KB (1,313 words) - 04:36, 29 December 2016
- ...ned off by default]) - note the implementation does not reflect the latest changes in the specification6 KB (834 words) - 15:31, 10 November 2012