Unobtrusive JavaScript - Revision history

ClueBot NG: Reverting possible vandalism by 197.48.88.119 to version by GreenC bot. Report False Positive? Thanks, ClueBot NG. (4365217) (Bot)

2024-12-19T18:25:29Z

Reverting possible vandalism by 197.48.88.119 to version by GreenC bot. Report False Positive? Thanks, ClueBot NG. (4365217) (Bot)

← Previous revision		Revision as of 18:25, 19 December 2024
Line 34:		Line 34:
	==References==		==References==
	{{Reflist}}		{{Reflist}}
	mohamed adham

	==Further reading==		==Further reading==

197.48.88.119: /* References */

2024-12-19T18:22:41Z

References

← Previous revision		Revision as of 18:22, 19 December 2024
Line 34:		Line 34:
	==References==		==References==
	{{Reflist}}		{{Reflist}}
			mohamed adham

	==Further reading==		==Further reading==

GreenC bot: Reformat 1 citation per :Category:CS1 errors: archive-url. Wayback Medic 2.5

2023-08-23T20:06:59Z

Reformat 1 citation per Category:CS1 errors: archive-url. Wayback Medic 2.5

← Previous revision		Revision as of 20:06, 23 August 2023
Line 1:		Line 1:
	{{Short description\|General approach to the use of JavaScript in web pages}}		{{Short description\|General approach to the use of JavaScript in web pages}}
	'''Unobtrusive JavaScript''' is a general approach to the use of [[client-side]] [[JavaScript]] in [[web page]]s so that if JavaScript features are partially or fully absent in a user's [[web browser]], then the user notices as little as possible any lack of the web page's JavaScript functionality.<ref name=Langridge2005/> The term has been used by different technical writers to emphasize different aspects of [[front-end web development]]. For some writers, the term has been understood more generally to refer to [[separation of concerns\|separation of functionality]] (the "behavior layer") from a web page's [[Markup language\|structure/content]] and [[Style sheet (web development)\|presentation]],<ref>{{cite web \|last=Keith \|first=Jeremy \|title=Behavioral Separation \|date=2006-06-20 \|url=https://www.alistapart.com/articles/behavioralseparation \|website=www.alistapart.com \|access-date=2007-01-27 \|quote=Separating out behavior from markup like this is called unobtrusive JavaScript.}}</ref> while other writers have used the term more precisely to refer to the use of [[progressive enhancement]] to support [[user agent]]s that lack certain JavaScript functionality and users that have disabled JavaScript.<ref>{{cite web \|last=Olsson \|first=Tommy \|title=Graceful Degradation & Progressive Enhancement \|date=2007-02-06 \|url=http://accessites.org/site/2007/02/graceful-degradation-progressive-enhancement/2 \|website=accessites.org \|archive-url=https://web.archive.org/web/20170517143009/http://accessites.org/site/2007/02/graceful-degradation-progressive-enhancement/2 \|archive-date=2017-07-18 \|access-date=2009-01-03 \|quote=Progressive enhancement when it comes to JavaScript is becoming more common these days. The key to this is known as unobtrusive JavaScript. An unobtrusive script is silently ignored by user agents that do not support it, but is applied by more capable devices. Just like an external style sheet.}}</ref> Following the latter definition, unobtrusive JavaScript contributes to [[web accessibility]] insofar as it helps ensure that all users—whatever their computing platform—get roughly equal access to all of the web page's information and functionality.<ref name=Flanagan2006/><ref>{{cite book \|last=Connor \|first=Joshue O. \|date=2012 \|chapter=Unobtrusive JavaScript \|title=Pro HTML5 Accessibility: Building an Inclusive Web \|location=Berkeley, CA \|publisher=[[Apress]] \|pages=[https://books.google.com/books?id=gdithJnztpUC&pg=PA71 71] \|isbn=9781430241942 \|oclc=757486357 \|doi=10.1007/978-1-4302-4195-9_3}}</ref>		'''Unobtrusive JavaScript''' is a general approach to the use of [[client-side]] [[JavaScript]] in [[web page]]s so that if JavaScript features are partially or fully absent in a user's [[web browser]], then the user notices as little as possible any lack of the web page's JavaScript functionality.<ref name=Langridge2005/> The term has been used by different technical writers to emphasize different aspects of [[front-end web development]]. For some writers, the term has been understood more generally to refer to [[separation of concerns\|separation of functionality]] (the "behavior layer") from a web page's [[Markup language\|structure/content]] and [[Style sheet (web development)\|presentation]],<ref>{{cite web \|last=Keith \|first=Jeremy \|title=Behavioral Separation \|date=2006-06-20 \|url=https://www.alistapart.com/articles/behavioralseparation \|website=www.alistapart.com \|access-date=2007-01-27 \|quote=Separating out behavior from markup like this is called unobtrusive JavaScript.}}</ref> while other writers have used the term more precisely to refer to the use of [[progressive enhancement]] to support [[user agent]]s that lack certain JavaScript functionality and users that have disabled JavaScript.<ref>{{cite web \|last=Olsson \|first=Tommy \|title=Graceful Degradation & Progressive Enhancement \|date=2007-02-06 \|url=http://accessites.org/site/2007/02/graceful-degradation-progressive-enhancement/2 \|website=accessites.org \|archive-url=https://web.archive.org/web/20170517143009/http://accessites.org/site/2007/02/graceful-degradation-progressive-enhancement/2 \|archive-date=2017-05-17 \|access-date=2009-01-03 \|quote=Progressive enhancement when it comes to JavaScript is becoming more common these days. The key to this is known as unobtrusive JavaScript. An unobtrusive script is silently ignored by user agents that do not support it, but is applied by more capable devices. Just like an external style sheet.}}</ref> Following the latter definition, unobtrusive JavaScript contributes to [[web accessibility]] insofar as it helps ensure that all users—whatever their computing platform—get roughly equal access to all of the web page's information and functionality.<ref name=Flanagan2006/><ref>{{cite book \|last=Connor \|first=Joshue O. \|date=2012 \|chapter=Unobtrusive JavaScript \|title=Pro HTML5 Accessibility: Building an Inclusive Web \|location=Berkeley, CA \|publisher=[[Apress]] \|pages=[https://books.google.com/books?id=gdithJnztpUC&pg=PA71 71] \|isbn=9781430241942 \|oclc=757486357 \|doi=10.1007/978-1-4302-4195-9_3}}</ref>

	==Overview==		==Overview==

Anton.bersh: Remove empty "See also" section

2022-03-18T08:57:35Z

Remove empty "See also" section

← Previous revision		Revision as of 08:57, 18 March 2022
Line 31:		Line 31:

	The broader definitions of unobtrusive JavaScript have much in common with general programming best practices, such as [[Information hiding\|encapsulation]] and [[abstraction layer]]s, avoidance of [[global variable]]s, meaningful [[naming conventions (programming)\|naming conventions]], use of appropriate [[design patterns]], and systematic [[software testing\|testing]].<ref>{{cite book \|last=White \|first=Alexei \|date=2009 \|chapter=Unobtrusive JavaScript \|title=JavaScript Programmer's Reference \|series=Wrox Programmer to Programmer \|location=Chichester, UK; Hoboken, NJ \|publisher=Wiley \|page=[https://books.google.com/books?id=XJrXl71TITIC&pg=PA311 311] \|isbn=9780470344729 \|oclc=421783941}}</ref>		The broader definitions of unobtrusive JavaScript have much in common with general programming best practices, such as [[Information hiding\|encapsulation]] and [[abstraction layer]]s, avoidance of [[global variable]]s, meaningful [[naming conventions (programming)\|naming conventions]], use of appropriate [[design patterns]], and systematic [[software testing\|testing]].<ref>{{cite book \|last=White \|first=Alexei \|date=2009 \|chapter=Unobtrusive JavaScript \|title=JavaScript Programmer's Reference \|series=Wrox Programmer to Programmer \|location=Chichester, UK; Hoboken, NJ \|publisher=Wiley \|page=[https://books.google.com/books?id=XJrXl71TITIC&pg=PA311 311] \|isbn=9780470344729 \|oclc=421783941}}</ref>

	==See also==

	==References==		==References==

Modussiccandi: Removing link(s) Wikipedia:Articles for deletion/Standards-compliant closed as delete (XFDcloser)

2022-03-18T08:19:32Z

Removing link(s) Wikipedia:Articles for deletion/Standards-compliant closed as delete (XFDcloser)

← Previous revision		Revision as of 08:19, 18 March 2022
Line 33:		Line 33:

	==See also==		==See also==
	* [[Standards compliance]]

	==References==		==References==

JJMC89 bot III: Moving :Category:Adaptive Web Design to :Category:Adaptive web design per Wikipedia:Categories for discussion/Speedy

2021-11-01T06:48:17Z

Moving Category:Adaptive Web Design to Category:Adaptive web design per Wikipedia:Categories for discussion/Speedy

← Previous revision		Revision as of 06:48, 1 November 2021
Line 56:		Line 56:
	[[Category:Web accessibility]]		[[Category:Web accessibility]]
	[[Category:Responsive web design]]		[[Category:Responsive web design]]
	[[Category:Adaptive ~~Web~~ ~~Design~~]]		[[Category:Adaptive web design]]

DJB3.14: /* top */ copyedit

2021-10-11T23:13:06Z

top: copyedit

← Previous revision		Revision as of 23:13, 11 October 2021
Line 1:		Line 1:
	{{Short description\|General approach to the use of JavaScript in web pages}}		{{Short description\|General approach to the use of JavaScript in web pages}}
	'''Unobtrusive JavaScript''' is a general approach to the use of [[client-side]] [[JavaScript]] in [[web page]]s so that if JavaScript features are partially or fully absent in a user's [[web browser]], then the user notices as little as possible any lack of the web page's JavaScript functionality.<ref name=Langridge2005/> The term has been used by different technical writers to emphasize different aspects of [[front-end web development]]. For some writers, the term has been understood more generally to refer to [[separation of concerns\|separation of functionality]] (the "behavior layer") from a web page's [[Markup language\|structure/content]] and [[Style sheet (web development)\|presentation]],<ref>{{cite web \|last=Keith \|first=Jeremy \|title=Behavioral Separation \|date=2006-06-20 \|url=https://www.alistapart.com/articles/behavioralseparation \|website=www.alistapart.com \|access-date=2007-01-27 \|quote=Separating out behavior from markup like this is called unobtrusive JavaScript.}}</ref> while other writers have used the term more precisely to refer to the use of [[progressive enhancement]] to support [[user agent]]s that lack certain JavaScript functionality and users that have disabled JavaScript.<ref>{{cite web \|last=Olsson \|first=Tommy \|title=Graceful Degradation & Progressive Enhancement \|date=2007-02-06 \|url=http://accessites.org/site/2007/02/graceful-degradation-progressive-enhancement/2 \|website=accessites.org \|archive-url=https://web.archive.org/web/20170517143009/http://accessites.org/site/2007/02/graceful-degradation-progressive-enhancement/2 \|archive-date=2017-07-18 \|access-date=2009-01-03 \|quote=Progressive enhancement when it comes to JavaScript is becoming more common these days. The key to this is known as unobtrusive JavaScript. An unobtrusive script is silently ignored by user agents that do not support it, but is applied by more capable devices. Just like an external style sheet.}}</ref> Following the latter definition, unobtrusive JavaScript contributes to [[web accessibility]] insofar as it helps ensure ~~that~~ that all users—whatever their computing platform—get roughly equal access to all of the web page's information and functionality.<ref name=Flanagan2006/><ref>{{cite book \|last=Connor \|first=Joshue O. \|date=2012 \|chapter=Unobtrusive JavaScript \|title=Pro HTML5 Accessibility: Building an Inclusive Web \|location=Berkeley, CA \|publisher=[[Apress]] \|pages=[https://books.google.com/books?id=gdithJnztpUC&pg=PA71 71] \|isbn=9781430241942 \|oclc=757486357 \|doi=10.1007/978-1-4302-4195-9_3}}</ref>		'''Unobtrusive JavaScript''' is a general approach to the use of [[client-side]] [[JavaScript]] in [[web page]]s so that if JavaScript features are partially or fully absent in a user's [[web browser]], then the user notices as little as possible any lack of the web page's JavaScript functionality.<ref name=Langridge2005/> The term has been used by different technical writers to emphasize different aspects of [[front-end web development]]. For some writers, the term has been understood more generally to refer to [[separation of concerns\|separation of functionality]] (the "behavior layer") from a web page's [[Markup language\|structure/content]] and [[Style sheet (web development)\|presentation]],<ref>{{cite web \|last=Keith \|first=Jeremy \|title=Behavioral Separation \|date=2006-06-20 \|url=https://www.alistapart.com/articles/behavioralseparation \|website=www.alistapart.com \|access-date=2007-01-27 \|quote=Separating out behavior from markup like this is called unobtrusive JavaScript.}}</ref> while other writers have used the term more precisely to refer to the use of [[progressive enhancement]] to support [[user agent]]s that lack certain JavaScript functionality and users that have disabled JavaScript.<ref>{{cite web \|last=Olsson \|first=Tommy \|title=Graceful Degradation & Progressive Enhancement \|date=2007-02-06 \|url=http://accessites.org/site/2007/02/graceful-degradation-progressive-enhancement/2 \|website=accessites.org \|archive-url=https://web.archive.org/web/20170517143009/http://accessites.org/site/2007/02/graceful-degradation-progressive-enhancement/2 \|archive-date=2017-07-18 \|access-date=2009-01-03 \|quote=Progressive enhancement when it comes to JavaScript is becoming more common these days. The key to this is known as unobtrusive JavaScript. An unobtrusive script is silently ignored by user agents that do not support it, but is applied by more capable devices. Just like an external style sheet.}}</ref> Following the latter definition, unobtrusive JavaScript contributes to [[web accessibility]] insofar as it helps ensure that all users—whatever their computing platform—get roughly equal access to all of the web page's information and functionality.<ref name=Flanagan2006/><ref>{{cite book \|last=Connor \|first=Joshue O. \|date=2012 \|chapter=Unobtrusive JavaScript \|title=Pro HTML5 Accessibility: Building an Inclusive Web \|location=Berkeley, CA \|publisher=[[Apress]] \|pages=[https://books.google.com/books?id=gdithJnztpUC&pg=PA71 71] \|isbn=9781430241942 \|oclc=757486357 \|doi=10.1007/978-1-4302-4195-9_3}}</ref>

	==Overview==		==Overview==

Qwerfjkl: Importing Wikidata short description: "General approach to the use of JavaScript in web pages" (Shortdesc helper)

2021-08-05T16:17:20Z

Importing Wikidata short description: "General approach to the use of JavaScript in web pages" (Shortdesc helper)

← Previous revision		Revision as of 16:17, 5 August 2021
Line 1:		Line 1:
			{{Short description\|General approach to the use of JavaScript in web pages}}
	'''Unobtrusive JavaScript''' is a general approach to the use of [[client-side]] [[JavaScript]] in [[web page]]s so that if JavaScript features are partially or fully absent in a user's [[web browser]], then the user notices as little as possible any lack of the web page's JavaScript functionality.<ref name=Langridge2005/> The term has been used by different technical writers to emphasize different aspects of [[front-end web development]]. For some writers, the term has been understood more generally to refer to [[separation of concerns\|separation of functionality]] (the "behavior layer") from a web page's [[Markup language\|structure/content]] and [[Style sheet (web development)\|presentation]],<ref>{{cite web \|last=Keith \|first=Jeremy \|title=Behavioral Separation \|date=2006-06-20 \|url=https://www.alistapart.com/articles/behavioralseparation \|website=www.alistapart.com \|access-date=2007-01-27 \|quote=Separating out behavior from markup like this is called unobtrusive JavaScript.}}</ref> while other writers have used the term more precisely to refer to the use of [[progressive enhancement]] to support [[user agent]]s that lack certain JavaScript functionality and users that have disabled JavaScript.<ref>{{cite web \|last=Olsson \|first=Tommy \|title=Graceful Degradation & Progressive Enhancement \|date=2007-02-06 \|url=http://accessites.org/site/2007/02/graceful-degradation-progressive-enhancement/2 \|website=accessites.org \|archive-url=https://web.archive.org/web/20170517143009/http://accessites.org/site/2007/02/graceful-degradation-progressive-enhancement/2 \|archive-date=2017-07-18 \|access-date=2009-01-03 \|quote=Progressive enhancement when it comes to JavaScript is becoming more common these days. The key to this is known as unobtrusive JavaScript. An unobtrusive script is silently ignored by user agents that do not support it, but is applied by more capable devices. Just like an external style sheet.}}</ref> Following the latter definition, unobtrusive JavaScript contributes to [[web accessibility]] insofar as it helps ensure that that all users—whatever their computing platform—get roughly equal access to all of the web page's information and functionality.<ref name=Flanagan2006/><ref>{{cite book \|last=Connor \|first=Joshue O. \|date=2012 \|chapter=Unobtrusive JavaScript \|title=Pro HTML5 Accessibility: Building an Inclusive Web \|location=Berkeley, CA \|publisher=[[Apress]] \|pages=[https://books.google.com/books?id=gdithJnztpUC&pg=PA71 71] \|isbn=9781430241942 \|oclc=757486357 \|doi=10.1007/978-1-4302-4195-9_3}}</ref>		'''Unobtrusive JavaScript''' is a general approach to the use of [[client-side]] [[JavaScript]] in [[web page]]s so that if JavaScript features are partially or fully absent in a user's [[web browser]], then the user notices as little as possible any lack of the web page's JavaScript functionality.<ref name=Langridge2005/> The term has been used by different technical writers to emphasize different aspects of [[front-end web development]]. For some writers, the term has been understood more generally to refer to [[separation of concerns\|separation of functionality]] (the "behavior layer") from a web page's [[Markup language\|structure/content]] and [[Style sheet (web development)\|presentation]],<ref>{{cite web \|last=Keith \|first=Jeremy \|title=Behavioral Separation \|date=2006-06-20 \|url=https://www.alistapart.com/articles/behavioralseparation \|website=www.alistapart.com \|access-date=2007-01-27 \|quote=Separating out behavior from markup like this is called unobtrusive JavaScript.}}</ref> while other writers have used the term more precisely to refer to the use of [[progressive enhancement]] to support [[user agent]]s that lack certain JavaScript functionality and users that have disabled JavaScript.<ref>{{cite web \|last=Olsson \|first=Tommy \|title=Graceful Degradation & Progressive Enhancement \|date=2007-02-06 \|url=http://accessites.org/site/2007/02/graceful-degradation-progressive-enhancement/2 \|website=accessites.org \|archive-url=https://web.archive.org/web/20170517143009/http://accessites.org/site/2007/02/graceful-degradation-progressive-enhancement/2 \|archive-date=2017-07-18 \|access-date=2009-01-03 \|quote=Progressive enhancement when it comes to JavaScript is becoming more common these days. The key to this is known as unobtrusive JavaScript. An unobtrusive script is silently ignored by user agents that do not support it, but is applied by more capable devices. Just like an external style sheet.}}</ref> Following the latter definition, unobtrusive JavaScript contributes to [[web accessibility]] insofar as it helps ensure that that all users—whatever their computing platform—get roughly equal access to all of the web page's information and functionality.<ref name=Flanagan2006/><ref>{{cite book \|last=Connor \|first=Joshue O. \|date=2012 \|chapter=Unobtrusive JavaScript \|title=Pro HTML5 Accessibility: Building an Inclusive Web \|location=Berkeley, CA \|publisher=[[Apress]] \|pages=[https://books.google.com/books?id=gdithJnztpUC&pg=PA71 71] \|isbn=9781430241942 \|oclc=757486357 \|doi=10.1007/978-1-4302-4195-9_3}}</ref>

Arjayay: Duplicate word removed

2021-07-05T15:59:37Z

Duplicate word removed

← Previous revision		Revision as of 15:59, 5 July 2021
Line 4:		Line 4:
	A typical [[client-side dynamic web page]] can be conceived as consisting of four parts: the [[Markup language\|marked-up]] content ([[HTML]]), the style sheet ([[CSS]]), [[client-side JavaScript]], and embedded objects such as images.<ref name=JSBible>{{cite book \|last1=Goodman \|first1=Danny \|author-link1=Danny Goodman \|last2=Morrison \|first2=Michael \|author-link2=Michael Morrison (author) \|last3=Novitski \|first3=Paul \|last4=Rayl \|first4=Tia Gustaff \|date=2010 \|chapter=JavaScript's Role in the World Wide Web and Beyond \|title=JavaScript Bible \|edition=7th \|location=Indianapolis, IN \|publisher=Wiley \|pages=3–13 \|isbn=9780470526910 \|oclc=435731997}}</ref>{{rp\|5}} The client-side JavaScript part can be conceived as enhancing the other parts by adding features or functionality that would not be possible without JavaScript.<ref name=JSBible/>{{rp\|3}}		A typical [[client-side dynamic web page]] can be conceived as consisting of four parts: the [[Markup language\|marked-up]] content ([[HTML]]), the style sheet ([[CSS]]), [[client-side JavaScript]], and embedded objects such as images.<ref name=JSBible>{{cite book \|last1=Goodman \|first1=Danny \|author-link1=Danny Goodman \|last2=Morrison \|first2=Michael \|author-link2=Michael Morrison (author) \|last3=Novitski \|first3=Paul \|last4=Rayl \|first4=Tia Gustaff \|date=2010 \|chapter=JavaScript's Role in the World Wide Web and Beyond \|title=JavaScript Bible \|edition=7th \|location=Indianapolis, IN \|publisher=Wiley \|pages=3–13 \|isbn=9780470526910 \|oclc=435731997}}</ref>{{rp\|5}} The client-side JavaScript part can be conceived as enhancing the other parts by adding features or functionality that would not be possible without JavaScript.<ref name=JSBible/>{{rp\|3}}

	The concept of "unobtrusiveness" in relation to client-side JavaScript was coined in 2002 by [[Stuart Langridge]]<ref name=Langridge2002>{{cite web \|url=http://www.netmag.co.uk/zine/dhtml-1/building-dynamic-websites \|title=Building dynamic websites \|website=www.netmag.co.uk \|date=2006-08-09 \|access-date=2010-05-18 \|archive-url=https://web.archive.org/web/20101205235951/http://www.netmag.co.uk/zine/dhtml-1/building-dynamic-websites \|archive-date=2010-12-05}}<!-- See "about the author" to validate the claim --></ref> in the article "Unobtrusive DHTML, and the power of unordered lists".<ref>{{cite web \|url=http://www.kryogenix.org/code/browser/aqlists/ \|title=Unobtrusive DHTML, and the power of unordered lists \|last=Langridge \|first=Stuart \|date=November 2002 \|access-date=2008-08-07 \|website=www.kryogenix.org \|archive-url=https://web.archive.org/web/20021204224748/http://www.kryogenix.org/code/browser/aqlists/ \|archive-date=2002-12-04 \|url-status=live}}</ref> In the article Langridge argued for a way to keep all JavaScript code, including event handlers, outside of the HTML when using [[dynamic HTML]] (DHTML).<ref name=Langridge2002/> He said that ~~the~~ the purpose of this kind of organization of code was "providing a better user experience for people whose browsers can support it, and {{em\|not affecting}} those whose browsers cannot", while also making scripting easier for [[web developer]]s.<ref name=Langridge2002/> Langridge later expanded upon this thought and emphasized that the core meaning of "unobtrusive" is that "if a given Web browser doesn't support the DHTML features you're using, that absence should affect the user experience as little as possible".<ref name=Langridge2005>{{cite book \|last=Langridge \|first=Stuart \|title=DHTML Utopia: Modern Web Design Using JavaScript & DOM \|location=Collingwood, VIC, Australia \|publisher=SitePoint \|year=2005 \|isbn=9780957921894 \|oclc=60690615 \|url-access=registration \|url=https://archive.org/details/dhtmlutopiamoder0000lang \|page=[https://archive.org/details/dhtmlutopiamoder0000lang/page/75 75] \|quote=An important design constraint when adding DHTML to your Websites is that it should be unobtrusive. By 'unobtrusive,' I mean that if a given Web browser doesn't support the DHTML features you're using, that absence should affect the user experience as little as possible. Errors should not be shown to the user: the site should be perfectly usable without the DHTML enhancements.}} (Reference to the first edition, since it shows how the author pioneered the concept.) The same passage is in an article excerpted from the book: {{cite web \|url=http://articles.sitepoint.com/article/dhtml-utopia-modern-web-design/4 \|title=DHTML Utopia: Modern Web Design Using JavaScript & DOM \|last=Langridge \|first=Stuart \|date=2005-06-01 \|access-date=2016-10-18 \|website=articles.sitepoint.com \|archive-url=https://web.archive.org/web/20100421102116/http://articles.sitepoint.com/article/dhtml-utopia-modern-web-design/4 \|archive-date=2010-04-21}}</ref> In other words, for Langridge, "unobtrusive" principally refers to users' experience of the absence of JavaScript features in a given situation.<ref name=Langridge2005/>		The concept of "unobtrusiveness" in relation to client-side JavaScript was coined in 2002 by [[Stuart Langridge]]<ref name=Langridge2002>{{cite web \|url=http://www.netmag.co.uk/zine/dhtml-1/building-dynamic-websites \|title=Building dynamic websites \|website=www.netmag.co.uk \|date=2006-08-09 \|access-date=2010-05-18 \|archive-url=https://web.archive.org/web/20101205235951/http://www.netmag.co.uk/zine/dhtml-1/building-dynamic-websites \|archive-date=2010-12-05}}<!-- See "about the author" to validate the claim --></ref> in the article "Unobtrusive DHTML, and the power of unordered lists".<ref>{{cite web \|url=http://www.kryogenix.org/code/browser/aqlists/ \|title=Unobtrusive DHTML, and the power of unordered lists \|last=Langridge \|first=Stuart \|date=November 2002 \|access-date=2008-08-07 \|website=www.kryogenix.org \|archive-url=https://web.archive.org/web/20021204224748/http://www.kryogenix.org/code/browser/aqlists/ \|archive-date=2002-12-04 \|url-status=live}}</ref> In the article Langridge argued for a way to keep all JavaScript code, including event handlers, outside of the HTML when using [[dynamic HTML]] (DHTML).<ref name=Langridge2002/> He said that the purpose of this kind of organization of code was "providing a better user experience for people whose browsers can support it, and {{em\|not affecting}} those whose browsers cannot", while also making scripting easier for [[web developer]]s.<ref name=Langridge2002/> Langridge later expanded upon this thought and emphasized that the core meaning of "unobtrusive" is that "if a given Web browser doesn't support the DHTML features you're using, that absence should affect the user experience as little as possible".<ref name=Langridge2005>{{cite book \|last=Langridge \|first=Stuart \|title=DHTML Utopia: Modern Web Design Using JavaScript & DOM \|location=Collingwood, VIC, Australia \|publisher=SitePoint \|year=2005 \|isbn=9780957921894 \|oclc=60690615 \|url-access=registration \|url=https://archive.org/details/dhtmlutopiamoder0000lang \|page=[https://archive.org/details/dhtmlutopiamoder0000lang/page/75 75] \|quote=An important design constraint when adding DHTML to your Websites is that it should be unobtrusive. By 'unobtrusive,' I mean that if a given Web browser doesn't support the DHTML features you're using, that absence should affect the user experience as little as possible. Errors should not be shown to the user: the site should be perfectly usable without the DHTML enhancements.}} (Reference to the first edition, since it shows how the author pioneered the concept.) The same passage is in an article excerpted from the book: {{cite web \|url=http://articles.sitepoint.com/article/dhtml-utopia-modern-web-design/4 \|title=DHTML Utopia: Modern Web Design Using JavaScript & DOM \|last=Langridge \|first=Stuart \|date=2005-06-01 \|access-date=2016-10-18 \|website=articles.sitepoint.com \|archive-url=https://web.archive.org/web/20100421102116/http://articles.sitepoint.com/article/dhtml-utopia-modern-web-design/4 \|archive-date=2010-04-21}}</ref> In other words, for Langridge, "unobtrusive" principally refers to users' experience of the absence of JavaScript features in a given situation.<ref name=Langridge2005/>

	==Variant definitions==		==Variant definitions==

Biogeographist: expanded lead section; trimmed WP:POV & WP:OR material that was complained about on the talk page; added references and #Further reading section; removed links from #See also section that are already in article body per WP:NOTSEEALSO

2021-07-05T02:52:41Z

expanded lead section; trimmed WP:POV & WP:OR material that was complained about on the talk page; added references and #Further reading section; removed links from #See also section that are already in article body per WP:NOTSEEALSO

Show changes