Choosing Standards Compliance Over Proprietary Practices - Archive of obsolete content
nd processes that an organization can use. at the high level, there are two primary types of standards: procedural (how do we do it) vs. technical (what do we follow). organizations implement internal procedural standards so they are able to operate efficiently. they may also incorporate external procedural and/or technical standards. technical standards have traditionally been pioneered through consortiums or standards bodies. the technical standards can be either public, standards-based or a proprietary de facto standard. the purpose of this document is to discuss and emphasize the importance of conforming to open technology standards that are external to the organization. let’s begin the discussion, however, by looking inward to internal procedures, processes and standards. why should orga...
...by following the guidelines that have been put into place, organizations like aol can enhance ...
...by following the guidelines that have been put into place, organizations like aol can enhance user experience, interoperability,...

Call Tree - Firefox Developer Tools
same as for the separate entry for sort() later in the list. this is telling us that some samples were taken in sort() itself, rather than in the functions it calls. sometimes there's more than one path back from an entry to the top level. let's expand the entry for swap(): there were 253 samples taken inside swap(). but swap() was reached by two different paths: both bubblesort() and selectionsort() use it. we can also see that 252 of the 253 samples in swap() were taken in the bubblesort() branch, and only one in the selectionsort() branch. this result means that bubble sort is even less efficient than we had thought! it can shoulder the blame for another 252 samples, or almost another 10% of the total cost. with this kind of digging, we can figure out the whole call graph, with associa...
...an we had thought! it can shoulder the blame for another 252 samples, or almost another 10% of the total cost. with this kind of digging, we can figure out the whole call graph, with associated sample count: sortall() // 8 -> sort() // 37 -> bubblesort() // 1345 -> swap() // 252 -> selectionsort() // 190 -> swap() // 1 -> quicksort() // 103 -> partition() // 12 platform data you'll also see some rows labeled gecko, input & events, and so on. these represent internal browser calls. this can be useful information too. if your site is making the browser work hard, this might not show up as samples recorded in ...
...gest group after bubblesort(). let's expand that: this result is telling us that 614 of those samples, or about 20% of the total cost, are coming from our sort() call. if we look at the code for sort(), it should be fairly obvious that the high platform data cost is coming from repeated calls to console.log(): function sort(unsorted) { console.log(bubblesort(unsorted)); console.log(selectionsort(unsorted)); console.log(quicksort(unsorted)); } it would certainly be worthwhile considering more efficient ways of implementing this. one thing to be aware of here is that idle time is classified as gecko, so parts of your profile where your javascript isn't running will contribute gecko samples. these aren't relevant to the performance of your site. by default, the call tree doesn't split...

Flame Chart - Firefox Developer Tools
ture. we'll use the same profile file as that used in the call tree page. in the call tree page, we figured out that the program call graph in that profile, and the associated sample count, looked like this: sortall() // 8 -> sort() // 37 -> bubblesort() // 1345 -> swap() // 252 -> selectionsort() // 190 -> swap() // 1 -> quicksort() // 103 -> partition() // 12 first, we'll just select the whole section in which the program was active: at the top, colored purple, is the sortall() call, running throughout the program from start to finish. underneath that, colored olive-green, are the calls it's making to so...
...th that, colored olive-green, are the calls it's making to sort(). underneath that, like the teeth of a comb, are all the calls being made to each sorting algorithm. let's zoom in: this slice is about 140 ms long, and shows us more details of the functions being called by sort(). the sort() code is just this: function sort(unsorted) { console.log(bubblesort(unsorted)); console.log(selectionsort(unsorted)); console.log(quicksort(unsorted)); } the markers labeled "bubb..." and colored olive-green are presumably bubblesort(). the ones colored plain green are presumably the other sort functions. even at a glance, we can see that the bubble sort blocks are much wider (of a longer duration) than the others. we can also see some functions being called from bubblesort(), colored purple. le...
...d from bubblesort(), colored purple. let's zoom in one more time: this slice is about 20ms long. we can see that the purple markers underneath bubblesort() are the calls to swap(). if you counted them all, the call tree view tells us that you'd see 253 of them. all the ones in this zoom are underneath bubblesort(), but according to the call tree view, the profile does contain one under selectionsort(). we can also see that two of the green markers are for selectionsort() and quicksort(), but we're also seeing calls to platform (gecko) code in between our calls to the sorting functions. it seems very likely that this is from the console.log() calls in sort(). ...

JXON - Archive of obsolete content
he comic parker & badger by cuadrado. see also: badgerfish convention. the following is a transcription of the parker convention paper (version 0.4), from the page “transformingrules” of the xml2json-xslt project site. this convention was written in order to regulate the conversion to json from xslt, so parts of it are futile for javascript. note: on october 29th, 2013, the world wide web consortium relased in a note on official algorithm for converting html5 microdata to json. however, html microdata is not html: microdata is a formatted subset of html. translation json the root element will be absorbed, for there is only one: <root>test</root> becomes "test" element names become object properties: <root><name>xml</name><encoding>ascii</encoding></root> becom...
...ample) of the first algorithm (verbosity level: 3) are not included. the jxon.unbuild() method utilises our reverse algorithm. therefore, all code considerations remain the same. ...

Index - MDN Web Docs Glossary: Definitions of Web-related terms
voip (voice over internet protocol) is a technology used to transmit voice messages over ip (internet protocol) networks. common voip packages include skype, msn messenger, yahoo and many more. everything transferrred through voip is digital. it is also known as ip telephony, or broadband telephony. the main reason for using voip technology is because of cost. ...
...is a technology used to transmit voice messages over ip (internet protocol) networks. common voip packages include skype, msn messenger, yahoo and many more. everything transferrred through voip is digital. it is also known as ip telephony, or broadband telephony. the main reason for using voip technology is because of cost. 485 w3c community, consortium, glossary, intro, w3c, web consortium the world wide web consortium (w3c) is an international body that maintains web-related rules and frameworks. 486 wai accessibility, glossary wai or web accessibility initiative is an effort by the world wide web consortium (w3c) to improve accessibility for people with various challenges, who may need a nonstandard browser or devices. 487 wcag accessi...

Sorting algorithms comparison - Firefox Developer Tools
es: the guide to the call tree and the guide to the flame chart. this program compares the performance of three different sorting algorithms: bubble sort selection sort quicksort it consists of the following functions: sortall() top-level function. iteratively (200 iterations) generates a randomized array and calls sort(). sort() calls each of bubblesort(), selectionsort(), quicksort() in turn and logs the result. bubblesort() implements a bubble sort, returning the sorted array. selectionsort() implements a selection sort, returning the sorted array. quicksort() implements quicksort, returning the sorted array. swap() helper function for bubblesort() and selectionsort(). partition() helper function for ...
...d array. swap() helper function for bubblesort() and selectionsort(). partition() helper function for quicksort(). its call graph looks like this: sortall() // (generate random array, then call sort) x 200 -> sort() // sort with each algorithm, log the result -> bubblesort() -> swap() -> selectionsort() -> swap() -> quicksort() -> partition() the implementations of the sorting algorithms in the program are taken from https://github.com/nzakas/computer-science-in-javascript/ and are used under the mit license. you can try out the example program here and clone the code here (be sure to check out the gh-pages branch). you can also download the specific profil...

GlobalEventHandlers - Web APIs
raised, i.e. when the user starts to make a new text selection on a web page. globaleventhandlers.onselectionchange is an eventhandler representing the code to be called when the selectionchange event is raised, i.e. when the text selected on a web page changes. globaleventhandlers.onshow is an eventhandler representing the code to be called when the show event is raised. globaleventhandlers.onsort is an eventhandler representing the code to be called when the sort event is raised. globaleventhandlers.onstalled is an eventhandler representing the code to be called when the stalled event is raised. globaleventhandlers.onsubmit is an eventhandler representing the code to be called when the submit event is raised. globaleventhandlers.onsuspend is an eventhandler representing the code ...
...ange and onpointerlockerror on document. it is experimentally implemented on globaleventhandlers. html living standardthe definition of 'globaleventhandlers' in that specification. living standard no change since the latest snapshot, html 5.1. html 5.1the definition of 'globaleventhandlers' in that specification. recommendation snapshot of html living standard. added onsort since the html5 snapshot. html5the definition of 'globaleventhandlers' in that specification. recommendation snapshot of html living standard. creation of globaleventhandlers (properties where on the target before it). ...

For Further Reading - XSLT: Extensible Stylesheet Language Transformations
on.com/xslt-doug-tidwell/dp/0596000537 learning xml, second edition author: erik t. ray length: 432 pages publisher: o'reilly media; 2 edition (september 22, 2003) isbn: 0596004206 as the title indicates, this is an overview of xml generally. chapter 6 is devoted specifically to xslt. ...
... articles hands-on xsl author: don r. ...

CSS3 - Archive of obsolete content
new modules are also added when new needs are identified. formally, there is no css3 standard per se . each module being standardized independently, the standard css consists of css2.1 amended and extended by the completed modules, not necessary all with the same level number. at each point of time, a snapshot of the css standard can be defined, listing css2.1 and the mature modules. the w3 consortium periodically publishes such snapshots, like in 2007, 2010, 2015, 2017, and 2018. though today no module with a level greater than 3 is standardized, this will change in the future. some modules, like selectors 4 or css borders and backgrounds level 4 already have an editor's draft, though they haven't yet reached the first published working draft status. css modules status completed modules...

Index - Archive of obsolete content
mentation. please edit only if an actual behavior differs from the described one. please do not edit only on the basis of another xbl specification. 701 event handlers no summary! 702 example sticky notes no summary! 703 xml in mozilla needshelp, needsupdate, xml mozilla has a relatively good support for xml. several world wide web consortium (w3c) recommendations and drafts from the xml family of specifications are supported, as well as other related technologies. 704 xpinstall xpinstall, xpinstall_api_reference no summary! 705 creating xpi installer modules xpinstall mozilla has introduced major changes to the way that themes and all the other parts of the ui are packaged. this new packag...

Links - Archive of obsolete content
some other skin related resources: learning css zvon.org the world wide web consortium ...

XML in Mozilla - Archive of obsolete content
this page is outdated. please help updating it with current information. supported core xml w3c recommendations the core xml support includes parsing xml without validation (we use the expat parser), displaying xml with css, manipulating xml documents with scripts via dom, associating stylesheets with xml documents, and namespaces in xml. the core support is very good with few bugs. dtds and other external entities mozilla does not load external entities from the web. ...

Archived Mozilla and build documentation - Archive of obsolete content
arn how the mozilla codebase works and how to take advantage of its technology in your own applications and extensions. this article is a jumping-off point to help you find those presentations. gecko - the smart embedding choice xbdesignmode.js xml in mozilla mozilla has a relatively good support for xml. several world wide web consortium (w3c) recommendations and drafts from the xml family of specifications are supported, as well as other related technologies. xpinstall xpjs components proposal draft 1.0 xre xtech 2005 presentations xtech 2006 presentations xul explorer xul explorer is a xulrunner app...

Using Web Standards in your Web Pages - Archive of obsolete content
ers are no longer the problem. the problem lies with designers and developers chained to the browser-quirk-oriented markup of the 1990s-often because they don't realize it is possible to support current standards while accommodating old browsers." -web standards project this article provides an overview of the process for upgrading the content of your web pages to conform to the world wide web consortium (w3c) web standards. the first 2 sections address exclusively validation issues, benefits of validation, deprecated elements, deprecated attributes. how to upgrade a webpage markup code to pass validation and how to implement css are addressed by providing recommendations, tutorials and references. the other sections address dom and dhtml coding practices which are at odds with the w3c web st...

Browser Detection and Cross Browser Support - Archive of obsolete content
e today and will become even less true as more browsers which support the w3c dom standards are introduced in the future. recommendations target the standards and not particular browsers while the period from 1994-2000 was dominated by incompatible non-standard browsers from netscape and microsoft, today the dominating factor in web development are the standards proposed by the world wide web consortium (w3c). standards are important for web developers due to the increased flexibility, power of presentation, support for users with disabilities to name just a few reasons. targeting your web content to particular vendors ignores the possibility that other browsers which support the same standards may be introduced in the future. a common problem on the web today is the assumption that the only...