Talk:Client-side JavaScript - Revision history

PrimeBOT: Replace magic links with templates per local RfC - BRFA

2017-07-06T22:44:07Z

Replace magic links with templates per local RfC - BRFA

← Previous revision		Revision as of 22:44, 6 July 2017
Line 4:		Line 4:
	\|title = JavaScript: JavaScript syntax, client-side JavaScript, JavaScript engine, Ajax (programming), Web interoperability, web accessibility, cross-site scripting, cross-site request forgery, ECMAScript, dynamic HTML		\|title = JavaScript: JavaScript syntax, client-side JavaScript, JavaScript engine, Ajax (programming), Web interoperability, web accessibility, cross-site scripting, cross-site request forgery, ECMAScript, dynamic HTML
	\|org = Alphascript Publishing		\|org = Alphascript Publishing
	\|comments = {{OCLC\|721316846}}, ISBN 9786130097844.		\|comments = {{OCLC\|721316846}}, {{ISBN\|9786130097844}}.
	\|bot=LivingBot		\|bot=LivingBot
	}}		}}

LivingBot: Bot adding {{backwardscopy}} template for VDM publication. Incorrect? If in doubt, revert. VDM have been known to include e.g. Georgia (state) when they mean Georgia (country), however (#112).

2011-06-19T21:05:12Z

Bot adding {{backwardscopy}} template for VDM publication. Incorrect? If in doubt, revert. VDM have been known to include e.g. Georgia (state) when they mean Georgia (country), however (#112).

← Previous revision		Revision as of 21:05, 19 June 2011
Line 1:		Line 1:
			{{Backwardscopy
			\|author = Miller, F. P., Vandome, A. F., & McBrewster, J.
			\|year = 2010
			\|title = JavaScript: JavaScript syntax, client-side JavaScript, JavaScript engine, Ajax (programming), Web interoperability, web accessibility, cross-site scripting, cross-site request forgery, ECMAScript, dynamic HTML
			\|org = Alphascript Publishing
			\|comments = {{OCLC\|721316846}}, ISBN 9786130097844.
			\|bot=LivingBot
			}}

	==Merge with JavaScript==		==Merge with JavaScript==
	I have proposed a merge with [[JavaScript]], please see the talk page in [[JavaScript]]. [[User:Bamkin\|Bamkin]] 19:02, 22 July 2007 (UTC)		I have proposed a merge with [[JavaScript]], please see the talk page in [[JavaScript]]. [[User:Bamkin\|Bamkin]] 19:02, 22 July 2007 (UTC)

Nigelj: You're right

2011-03-12T20:57:23Z

You're right

← Previous revision		Revision as of 20:57, 12 March 2011
Line 1:		Line 1:
	==Merge with JavaScript==		==Merge with JavaScript==
	I have proposed a merge with [[JavaScript]], please see the talk page in [[JavaScript]]. [[User:Bamkin\|Bamkin]] 19:02, 22 July 2007 (UTC)		I have proposed a merge with [[JavaScript]], please see the talk page in [[JavaScript]]. [[User:Bamkin\|Bamkin]] 19:02, 22 July 2007 (UTC)

⚫	==Citation Needed==
⚫	"Older browsers typically require JavaScript to begin with:"
⚫	Which older browsers require this? [[User:Cmcculloh\|Cmcculloh]] ([[User talk:Cmcculloh\|talk]]) 19:52, 10 March 2011 (UTC)

	==Reference to base2 project==		==Reference to base2 project==
Line 33:		Line 29:

	Unless otherwise specified in the article for some purpose, it should be assumed that a JavaScript sample code is designed to work with Internet Explorer. That should mean <code> type="text/javascript" </code> should be used instead of <code> type="application/javascript"</code>. One person's idea of ideal IANA compliance shouldn't get in the way of the users' and framework developers' intention of writing cross browser code. In example code, "application/javascript" should not replace "text/javascript" without reason and especially without warning. Furthermore "text/javascript" is supported in HTML 5 and it is the default type attribute value when not specifically coded. —[[User:Tokek\|Tokek]] ([[User talk:Tokek\|talk]]) 11:03, 16 November 2009 (UTC)		Unless otherwise specified in the article for some purpose, it should be assumed that a JavaScript sample code is designed to work with Internet Explorer. That should mean <code> type="text/javascript" </code> should be used instead of <code> type="application/javascript"</code>. One person's idea of ideal IANA compliance shouldn't get in the way of the users' and framework developers' intention of writing cross browser code. In example code, "application/javascript" should not replace "text/javascript" without reason and especially without warning. Furthermore "text/javascript" is supported in HTML 5 and it is the default type attribute value when not specifically coded. —[[User:Tokek\|Tokek]] ([[User talk:Tokek\|talk]]) 11:03, 16 November 2009 (UTC)

		⚫	==Citation Needed==
		⚫	"Older browsers typically require JavaScript to begin with:"
		⚫	Which older browsers require this? [[User:Cmcculloh\|Cmcculloh]] ([[User talk:Cmcculloh\|talk]]) 19:52, 10 March 2011 (UTC)
			:[I moved this new thread to the bottom, where it should be]. You're right, that section contained a lot of barely comprehensible outdated tosh. [http://en.wikipedia.org/w/index.php?title=Client-side_JavaScript&action=historysubmit&diff=418509011&oldid=413953000 I've tried] to tidy it up, but it's time to move this article into the 21st century generally. --[[User:Nigelj\|Nigelj]] ([[User talk:Nigelj\|talk]]) 20:57, 12 March 2011 (UTC)

Cmcculloh: requested citation

2011-03-10T19:52:17Z

requested citation

← Previous revision		Revision as of 19:52, 10 March 2011
Line 1:		Line 1:
	==Merge with JavaScript==		==Merge with JavaScript==
	I have proposed a merge with [[JavaScript]], please see the talk page in [[JavaScript]]. [[User:Bamkin\|Bamkin]] 19:02, 22 July 2007 (UTC)		I have proposed a merge with [[JavaScript]], please see the talk page in [[JavaScript]]. [[User:Bamkin\|Bamkin]] 19:02, 22 July 2007 (UTC)

			==Citation Needed==
			"Older browsers typically require JavaScript to begin with:"
			Which older browsers require this? [[User:Cmcculloh\|Cmcculloh]] ([[User talk:Cmcculloh\|talk]]) 19:52, 10 March 2011 (UTC)

	==Reference to base2 project==		==Reference to base2 project==

Tokek: /* type="application/javascript" in Wikipedia sample codes considered harmful (obviously) */ new section

2009-11-16T11:03:03Z

type="application/javascript" in Wikipedia sample codes considered harmful (obviously): new section

← Previous revision		Revision as of 11:03, 16 November 2009
Line 25:		Line 25:

	What is the rationale behind not allowing Client-Side JavaScript to invoke a 'Save-As' dialog? I can't imagine that the security would be any different than linking to a file, since both could contain identical information and could be called at the same time. This seems to be crippling - "you can make any app you want in JavaScript, so long as you never need to <i>save a file</i>." JavaScript could truly become the 'does everything' programming language if it had this one ability. <span style="font-size: smaller;" class="autosigned">—Preceding [[Wikipedia:Signatures\|unsigned]] comment added by [[Special:Contributions/70.192.2.92\|70.192.2.92]] ([[User talk:70.192.2.92\|talk]]) 07:52, 8 August 2009 (UTC)</span><!-- Template:UnsignedIP --> <!--Autosigned by SineBot-->		What is the rationale behind not allowing Client-Side JavaScript to invoke a 'Save-As' dialog? I can't imagine that the security would be any different than linking to a file, since both could contain identical information and could be called at the same time. This seems to be crippling - "you can make any app you want in JavaScript, so long as you never need to <i>save a file</i>." JavaScript could truly become the 'does everything' programming language if it had this one ability. <span style="font-size: smaller;" class="autosigned">—Preceding [[Wikipedia:Signatures\|unsigned]] comment added by [[Special:Contributions/70.192.2.92\|70.192.2.92]] ([[User talk:70.192.2.92\|talk]]) 07:52, 8 August 2009 (UTC)</span><!-- Template:UnsignedIP --> <!--Autosigned by SineBot-->

			== type="application/javascript" in Wikipedia sample codes considered harmful (obviously) ==

			Unless otherwise specified in the article for some purpose, it should be assumed that a JavaScript sample code is designed to work with Internet Explorer. That should mean <code> type="text/javascript" </code> should be used instead of <code> type="application/javascript"</code>. One person's idea of ideal IANA compliance shouldn't get in the way of the users' and framework developers' intention of writing cross browser code. In example code, "application/javascript" should not replace "text/javascript" without reason and especially without warning. Furthermore "text/javascript" is supported in HTML 5 and it is the default type attribute value when not specifically coded. —[[User:Tokek\|Tokek]] ([[User talk:Tokek\|talk]]) 11:03, 16 November 2009 (UTC)

CardinalDan: Reverted edits by 69.237.151.124 (talk) to last version by 78.27.52.235

2009-11-02T00:29:07Z

Reverted edits by 69.237.151.124 (talk) to last version by 78.27.52.235

Show changes

69.237.151.124: New-Player. Thank you.~~~~~

2009-10-31T20:11:10Z

New-Player. Thank you.~~~~~

Show changes

78.27.52.235: /* MIME type */

2009-10-06T22:20:51Z

MIME type

← Previous revision		Revision as of 22:20, 6 October 2009
Line 18:		Line 18:

	According to <http://www.ietf.org/rfc/rfc4329.txt>, the "new" MIME type for JavaScript is "application/javascript" and not "text/javascript". As I do not know if changing this works well with contemporary webbrowsers, I better leave it for someone more knowledged... [[Special:Contributions/84.189.219.143\|84.189.219.143]] ([[User talk:84.189.219.143\|talk]]) 00:22, 5 July 2008 (UTC)		According to <http://www.ietf.org/rfc/rfc4329.txt>, the "new" MIME type for JavaScript is "application/javascript" and not "text/javascript". As I do not know if changing this works well with contemporary webbrowsers, I better leave it for someone more knowledged... [[Special:Contributions/84.189.219.143\|84.189.219.143]] ([[User talk:84.189.219.143\|talk]]) 00:22, 5 July 2008 (UTC)

			I added something about the missing support for application/javascript in Internet Explorer. Maybe someone can rewrite that section to clarify it a bit.<br />
			[[Special:Contributions/78.27.52.235\|78.27.52.235]] ([[User talk:78.27.52.235\|talk]]) 22:20, 6 October 2009 (UTC)

	== Save-As ==		== Save-As ==

SineBot: Signing comment by 70.192.2.92 - ""

2009-08-08T07:53:49Z

Signing comment by 70.192.2.92 - ""

← Previous revision		Revision as of 07:53, 8 August 2009
Line 21:		Line 21:
	== Save-As ==		== Save-As ==

	What is the rationale behind not allowing Client-Side JavaScript to invoke a 'Save-As' dialog? I can't imagine that the security would be any different than linking to a file, since both could contain identical information and could be called at the same time. This seems to be crippling - "you can make any app you want in JavaScript, so long as you never need to <i>save a file</i>." JavaScript could truly become the 'does everything' programming language if it had this one ability.		What is the rationale behind not allowing Client-Side JavaScript to invoke a 'Save-As' dialog? I can't imagine that the security would be any different than linking to a file, since both could contain identical information and could be called at the same time. This seems to be crippling - "you can make any app you want in JavaScript, so long as you never need to <i>save a file</i>." JavaScript could truly become the 'does everything' programming language if it had this one ability. <span style="font-size: smaller;" class="autosigned">—Preceding [[Wikipedia:Signatures\|unsigned]] comment added by [[Special:Contributions/70.192.2.92\|70.192.2.92]] ([[User talk:70.192.2.92\|talk]]) 07:52, 8 August 2009 (UTC)</span><!-- Template:UnsignedIP --> <!--Autosigned by SineBot-->

70.192.2.92 at 07:52, 8 August 2009

2009-08-08T07:52:26Z

← Previous revision		Revision as of 07:52, 8 August 2009
Line 18:		Line 18:

	According to <http://www.ietf.org/rfc/rfc4329.txt>, the "new" MIME type for JavaScript is "application/javascript" and not "text/javascript". As I do not know if changing this works well with contemporary webbrowsers, I better leave it for someone more knowledged... [[Special:Contributions/84.189.219.143\|84.189.219.143]] ([[User talk:84.189.219.143\|talk]]) 00:22, 5 July 2008 (UTC)		According to <http://www.ietf.org/rfc/rfc4329.txt>, the "new" MIME type for JavaScript is "application/javascript" and not "text/javascript". As I do not know if changing this works well with contemporary webbrowsers, I better leave it for someone more knowledged... [[Special:Contributions/84.189.219.143\|84.189.219.143]] ([[User talk:84.189.219.143\|talk]]) 00:22, 5 July 2008 (UTC)

			== Save-As ==

			What is the rationale behind not allowing Client-Side JavaScript to invoke a 'Save-As' dialog? I can't imagine that the security would be any different than linking to a file, since both could contain identical information and could be called at the same time. This seems to be crippling - "you can make any app you want in JavaScript, so long as you never need to <i>save a file</i>." JavaScript could truly become the 'does everything' programming language if it had this one ability.