Internet Browser - Revision history

Danny8376: info for 11.14 spider

2025-09-21T07:18:14Z

info for 11.14 spider

← Older revision		Revision as of 11:18, 21 September 2025
Line 602:		Line 602:
	\| v11297		\| v11297
	\| [[11.9.0-42]]		\| [[11.9.0-42]]
			\| See below.
			\|-
			\| 1.7639
			\| v12288
			\| [[11.14.0-46]]
	\| See below.		\| See below.
	\|-		\|-

Danny8376: add version and user-agent for 11.15(-11.17)

2025-09-21T03:03:23Z

add version and user-agent for 11.15(-11.17)

← Older revision		Revision as of 07:03, 21 September 2025
Line 134:		Line 134:
	\| v11264		\| v11264
	\| [[11.14.0-46]]		\| [[11.14.0-46]]
			\| See below.
			\|-
			\| 1.12.10178
			\| Mozilla/5.0 (New Nintendo 3DS like iPhone) AppleWebKit/536.30 (KHTML, like Gecko) NX/3.0.0.5.24 Mobile NintendoBrowser/1.12.10178.<region>
			\| v12289
			\| [[11.15.0-47]]
	\| See below.		\| See below.
	\|}		\|}
Line 598:		Line 604:
	\| See below.		\| See below.
	\|-		\|-
	\| 1.~~7639~~		\| 1.7642
	\| ~~v12288~~		\| v13313
	\| [[11.14.0-46]]		\| [[11.15.0-47]]
	\| See below.		\| See below.
	\|}		\|}

CorbinDavenport: Update link to ImageShare

2023-04-02T18:39:17Z

Update link to ImageShare

← Older revision		Revision as of 22:39, 2 April 2023
Line 983:		Line 983:
	<!-- If you have a website that demonstrates these techniques, place it here! -->		<!-- If you have a website that demonstrates these techniques, place it here! -->
	* [http://www.nintendo.com/3ds/internetbrowser/bookmarks Nintendo 3DS Bookmarks]: This is the first bookmark pre-installed in the browser.		* [http://www.nintendo.com/3ds/internetbrowser/bookmarks Nintendo 3DS Bookmarks]: This is the first bookmark pre-installed in the browser.
	* [~~https~~://~~imgsharetool.herokuapp~~.com ImageShare]: Image uploader for the 3DS ([https://github.com/corbindavenport/~~image-share~~ source code])		* [http://theimageshare.com ImageShare]: Image uploader for the 3DS ([https://github.com/corbindavenport/imageshare source code])
	* [http://3ds.andysmith.co.uk/jFox.html jFox] (Short URL: http://bit.ly/iB7FqW)		* [http://3ds.andysmith.co.uk/jFox.html jFox] (Short URL: http://bit.ly/iB7FqW)
	* [http://ditto3d.com/3ds Ditto3D (Dead Link)] (Short URL: http://bit.ly/oVreWA)		* [http://ditto3d.com/3ds Ditto3D (Dead Link)] (Short URL: http://bit.ly/oVreWA)

Tonyzamboney: /* Notes */ Refresh rate and webkitRequestAnimationFrame

2023-03-11T14:26:56Z

Notes: Refresh rate and webkitRequestAnimationFrame

← Older revision		Revision as of 17:26, 11 March 2023
Line 481:		Line 481:
	* Favicons can be changed using Javascript, but they become unchangeable once the document's <em>readystatechange</em> event finishes firing with a ready state of "complete".		* Favicons can be changed using Javascript, but they become unchangeable once the document's <em>readystatechange</em> event finishes firing with a ready state of "complete".
	* Focusing on text-editable elements via Javascript will always open the keyboard.		* Focusing on text-editable elements via Javascript will always open the keyboard.
			* Webpage content is usually rendered at 30 FPS despite the <code>webkitRequestAnimationFrame</code> function allowing code to run at a rate of 60 FPS.
			** As a result, display-related routines may only show half of their intended updates.
			** This issue can be mitigated by rendering on every other frame. However, various factors (such as touchscreen input and sleep mode) make this fairly inconsistent.

	== Old3DS browser ==		== Old3DS browser ==

Tonyzamboney: /* Other details */ setFillColor and setStrokeColor use floats, not RGB565

2023-03-11T13:52:13Z

Other details: setFillColor and setStrokeColor use floats, not RGB565

← Older revision		Revision as of 16:52, 11 March 2023
Line 878:		Line 878:
	* HTML5Test.com say that Drag and drop is supported but it's not (code on WebKit is ready, but it's not implemented on interface of browser)		* HTML5Test.com say that Drag and drop is supported but it's not (code on WebKit is ready, but it's not implemented on interface of browser)
	* Webpages are rendered with the RGB565 color format.		* Webpages are rendered with the RGB565 color format.
	** Most RGB colors on the web are specified in RGB8 format, but the 2D canvas <code>setFillColor</code> and <code>setStrokeColor</code> functions accept RGB565 colors when provided with parameters for red, green, blue, and alpha, respectively.

	==Tips==		==Tips==

Tonyzamboney: /* Gamepad */ Unused buttons

2023-01-20T06:33:06Z

Gamepad: Unused buttons

← Older revision		Revision as of 09:33, 20 January 2023
Line 456:		Line 456:
	\| 9 \|\| Start		\| 9 \|\| Start
	\|-		\|-
	\| 10 \|\| ~~Unknown~~		\| 10 \|\| Unused
	\|-		\|-
	\| 11 \|\| ~~Unknown~~		\| 11 \|\| Unused
	\|-		\|-
	\| 12 \|\| Up		\| 12 \|\| Up
Line 469:		Line 469:
	\|}		\|}

	Each ~~number~~ is 0 while ~~its associated~~ button is not pressed, and 1 while the button is pressed.		Each button's value is 0 while the button is not pressed, and 1 while the button is pressed.

	~~The two unknown button numbers may have been intended for~~ the ~~Home~~ and ~~Power buttons, but they~~ are ~~always 0~~, ~~even if~~ the ~~web browser is used while the Home and/or Power buttons are pressed~~.		Based on the Gamepad API's specifications, buttons 10 and 11 are reserved for left stick presses and right stick presses respectively, which the 3DS does not support.

	==== Notes ====		==== Notes ====

Tonyzamboney: /* Detect User Agent */ Mobile site mode, misc. improvements

2022-12-20T22:15:00Z

Detect User Agent: Mobile site mode, misc. improvements

← Older revision		Revision as of 01:15, 21 December 2022
Line 884:		Line 884:
	=== Detect User Agent ===		=== Detect User Agent ===

	To detect if the user agent is Nintendo 3DS Browser :		To detect if the user agent is the Nintendo 3DS Internet Browser (not including mobile site mode):

	<script type="text/javascript">		<script type="text/javascript">
	if (navigator.userAgent.indexOf('Nintendo 3DS') == -1) { //If the ~~UserAgent is~~ not "Nintendo 3DS"		if(navigator.userAgent.indexOf("Nintendo 3DS") == -1) { // If the user agent does not contain "Nintendo 3DS"
	location.replace('http://www.3dbrew.org'); //Redirect to ~~an other~~ page		location.replace("http://www.3dbrew.org"); // Redirect to another page
	}		}
	</script>		</script>

	* You can check <em>navigator.platform=="Nintendo 3DS"</em> as well.		* You can check using <code>navigator.platform.indexOf("Nintendo 3DS") > -1</code> as well.
			* The New 3DS Internet Browser's "Request Mobile Sites" setting affects the user agent. To detect if the New 3DS Internet Browser is being used with this option enabled, use <code>screen.pixelDepth == 16 && navigator.platform == "iPhone"</code>.
			** This relies on the fact that the internet browser renders its webpages in 16-bit color, which is (hopefully?) not possible with a real iPhone.
			** Keep in mind that the previous browser-detection examples do not account for this setting.

	=== Scrolling ===		=== Scrolling ===

Tonyzamboney: /* Gamepad */ Formatting and performance hint

2022-11-18T15:09:59Z

Gamepad: Formatting and performance hint

← Older revision		Revision as of 18:09, 18 November 2022
Line 412:		Line 412:
	The browser's now-outdated gamepad API provides information about the states of the circle pad, C-stick, and every button aside from the Home and Power buttons. The gamepad, which has an ID of <code>New Nintendo 3DS Controller</code>, is contained within the array returned by the <code>navigator.webkitGetGamepads</code> function.		The browser's now-outdated gamepad API provides information about the states of the circle pad, C-stick, and every button aside from the Home and Power buttons. The gamepad, which has an ID of <code>New Nintendo 3DS Controller</code>, is contained within the array returned by the <code>navigator.webkitGetGamepads</code> function.

			Both of the gamepad's arrays, which contain the states of various inputs, seem to be reconstructed each time they are accessed via their gamepad object. It is not known if the values within the arrays can update upon each access of the array, but the values <em>can</em> update frequently enough to obtain accurate readings of the system's controls.

			===== Axes =====
	The gamepad's <code>axes</code> array contains four floating-point numbers in the following order:		The gamepad's <code>axes</code> array contains four floating-point numbers in the following order:

Line 428:		Line 431:
	Each coordinate ranges from -1.0 (left/up) to 1.0 (right/down). Neutral position is indicated by 0.0. Drift and/or inaccurate calibration may make these exact values unattainable.		Each coordinate ranges from -1.0 (left/up) to 1.0 (right/down). Neutral position is indicated by 0.0. Drift and/or inaccurate calibration may make these exact values unattainable.

			===== Buttons =====
	The gamepad's <code>buttons</code> array contains numbers for the following numbers:		The gamepad's <code>buttons</code> array contains numbers for the following numbers:
	{\|class="wikitable" width="20%"		{\|class="wikitable" width="20%"

Tonyzamboney: Meta viewport info + minor tweaks

2022-11-17T13:40:57Z

Meta viewport info + minor tweaks

← Older revision		Revision as of 16:40, 17 November 2022
Line 470:		Line 470:

	==== Notes ====		==== Notes ====
			* Viewport information can be specified with the <meta> element.
	* The html "color" <input> type is not supported.		* The html "color" <input> type is not supported.
	* 3D images appear as their right-eye image within webpages.		* 3D images appear as their right-eye image within webpages.
	* Webpages are locked to the bottom screen when zooming is disabled, the webpage's initial scale is ~~100%~~, and the entire webpage can fit within the bottom screen's dimensions (320x212).		* Webpages are locked to the bottom screen when zooming is disabled, the webpage's initial scale is 1, and the entire webpage can fit within the bottom screen's dimensions (320x212).
	* Interactable elements that are positioned partially outside of the bottom screen can temporarily be moved further inside the bottom screen by tapping them with the touchscreen.		* Interactable elements that are positioned partially outside of the bottom screen can temporarily be moved further inside the bottom screen by tapping them with the touchscreen.
	* Favicons can be changed using Javascript, but they become unchangeable once the document's <em>readystatechange</em> event finishes firing with a ready state of "complete".		* Favicons can be changed using Javascript, but they become unchangeable once the document's <em>readystatechange</em> event finishes firing with a ready state of "complete".
Line 940:		Line 941:
	The touch screen resolution is 320×240. However, the viewable area in the browser is <b>320×212</b> <em>or</em> <b>320×240</b>, depending on if the bottom browser bar is visible. The New3DS browser's bottom bar can hidden by scrolling and/or attempting to zoom in/out with the C-stick, unless scrolling and zooming have both been disabled.		The touch screen resolution is 320×240. However, the viewable area in the browser is <b>320×212</b> <em>or</em> <b>320×240</b>, depending on if the bottom browser bar is visible. The New3DS browser's bottom bar can hidden by scrolling and/or attempting to zoom in/out with the C-stick, unless scrolling and zooming have both been disabled.

	You can have a page span both screens. However, the browser will behave as if the bottom screen is the only active screen and the top screen is scrolled off. This is important when computing CSS coordinates. Items positioned from the "bottom" will be positioned based on the height of the bottom screen, not the cumulative ~~heights~~ of both screens.		You can have a page span both screens. However, the browser will behave as if the bottom screen is the only active screen and the top screen is scrolled off. This is important when computing CSS coordinates. Items positioned from the "bottom" will be positioned based on the height of the bottom screen, not the cumulative height of both screens.

	== Using Both Screens ==		== Using Both Screens ==
Line 968:		Line 969:
	}, 0);		}, 0);

	This automatically resets the position if the user accidentally scrolls the page. Zooming should probably also be disabled by adding <code>user-scalable=no</code> to the <meta> viewport element.		This automatically resets the position if the user accidentally scrolls the page. Zooming should probably also be disabled by adding <code>user-scalable=no</code> to the <meta> viewport element, though this will only have an effect in the New3DS browser.

	==Example Sites==		==Example Sites==

Tonyzamboney: /* Screen Resolution */ Bottom screen height

2022-11-17T13:21:11Z

Screen Resolution: Bottom screen height

← Older revision		Revision as of 16:21, 17 November 2022
Line 938:		Line 938:
	The up screen resolution is 400×240. However, the viewable area in the browser is only <b>400×215</b>.		The up screen resolution is 400×240. However, the viewable area in the browser is only <b>400×215</b>.

	The touch screen resolution is 320×240. However, the viewable area in the browser is ~~only~~ <b>320×212</b>.		The touch screen resolution is 320×240. However, the viewable area in the browser is <b>320×212</b> <em>or</em> <b>320×240</b>, depending on if the bottom browser bar is visible. The New3DS browser's bottom bar can hidden by scrolling and/or attempting to zoom in/out with the C-stick, unless scrolling and zooming have both been disabled.

	You can have a page span both screens. However, the browser will behave as if the bottom screen is the only active screen and the top screen is scrolled off. This is important when computing CSS coordinates. Items positioned from "bottom" will be positioned based on ~~215px and~~ not the ~~full 427px~~ of both screens.		You can have a page span both screens. However, the browser will behave as if the bottom screen is the only active screen and the top screen is scrolled off. This is important when computing CSS coordinates. Items positioned from the "bottom" will be positioned based on the height of the bottom screen, not the cumulative heights of both screens.

	== Using Both Screens ==		== Using Both Screens ==