Following
In many situations, the Script DOM Element is a good choice. It works in all browsers, doesn't have any cross-site scripting restrictions, is fairly simple to implement, and is well understood. The one catch is that it doesn't preserve execution order across all browsers.
Inserting script tags is the approach most libraries use for basic asynchronous script loading. Preserving order is problematic and requires the use of several different solutions to accomplish it.
The most …
the unresponsive DOM/web page due some broken piece of JavaScript able to make everything else stuck regardless the number of CPU and WebWorkers the Browser can handle
the " close window/tab " explicit action that takes ages due some greedy onunload operation
any sort of security issue
the change/update that requires a page reload
We are all in the same field Architecture matters, experience matters, performances matter, investigations matter, code quality matter, unit …
John Allsopp lets us in on the now well-supported DOM selectors such as getElementsByClassName and querySelector/querySelectorAll , which should ideally eventually replace DOM-helper libraries
Some interesting discussion on WebSQL vs indexedDB on Google+.
Superpacking JS Demos - helpful for those competing in JS1K, but not really practical for most folks.
Looks like Joe Hewitt is working on updates to Scrollability , and he seems to think …
HTML
Thanks to John Dyer and McGurk for contributing last week.
DOM
Thanks to Neil Rashbrook for his contributions last week.
What would that leave us with? CSS, DOM & JS APIs, HTML, a11y, i18n, and all the other stuff that has legs out on the public web. More to the point, it would have the beneficial effect of re-focusing the organization around getting HTML5 done, getting DOM APIs done that don't suck for JavaScript on the altar of IDL "language neutrality", etc.
Organizationally, it would leave the W3C in a much leaner, more focused place. It's much easier to build a focused …
…the conference. The focus of this doc sprint will naturally be docs for JavaScript and DOM. We hope to encourage attendees at the conference to contribute at least a little to improving the JS and DOM docs on MDN. I and a handful of MDN community members will be there to show them how.
To that end, we want to tag as many JS and DOM articles as possible, with tags indicating what work needs to be done on those articles. That way, anybody dropping in during the sprint (or anytime …
…explains DOM as a reasonable prototype chain. But it's only the beginning. The DOM is in terrible shape, and not due to implementation differences. The malign neglect of IDL-addled designs, the ghosts of dead-end XML experiments, and endless cruft will plague any language that sidles up to it. Until we get a real Component Model , a better CSS OM, and some sort of a pragma for DOM that allows us to fix DOM's abhorrent JS bindings, we'll continue to be hostage …
…was recently fussing over how developers don't tend to separate their DOM logic/interfaces from their JavaScript "business logic". Fuss as I might, I left the tirade rather open-ended, and that's because I wasn't sure that it was really a bad thing.
Either way, since JavaScript and the DOM are bunking together, we may as well make it safe — OOP safe.
For fun, let's see how this might look:
/* * Word * A class that encapsulates a word */ …
…child element. It's more efficient for dynamic content or highly interactive pages with a lot of DOM elements.
Example var myElement = $('myElement'); var request = new Request({ // other options onSuccess: function(text){ myElement.set('html', text); // No need to attach more click events. } }); // Adding the event, notice the :relay syntax with the selector that matches the target element inside of myElement. // Every click on an anchor-tag inside …
And again the HTML standard was trimmed some more. This time the parsing APIs ( innerHTML and friends) were taken out and integrated into DOM Parsing and Serialization . The upside of this is that the APIs now apply more generically and can also be used with MathML and SVG (well, once implementors adopt the changes).
W3C WebApps WG
At the W3C WebApps WG the DOM standard is starting to take shape. Aligning implementations on their implementation of the DOM…