<html>
<head>
<meta http-equiv="Content-Type" content="text/html;
charset=windows-1252">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<div class="moz-cite-prefix">Hi Albert,</div>
<div class="moz-cite-prefix"><br>
</div>
<div class="moz-cite-prefix">I think it is important to make a
distinction between a single web page (that is in 3D) opening up
many 2D pages and allowing the user to interact with each of them
separately and a browser application (e.g., replacement for
Chrome) that does more or less the same thing.</div>
<div class="moz-cite-prefix"><br>
</div>
<div class="moz-cite-prefix">This example presents a potential
security issue. In the first case, the page application (typically
written in JavaScript) must maintain separation between the
various external pages; otherwise one page could capture the
contents of another site. The existing structure in the browsers
works at preventing this sort of operation by preventing
JavaScript from one page from accessing the contents of another
page (unless permission is explicitly granted). This extends to
even off-screen rendering and grabbing of a web page to use as a
texture in a 3D world.<br>
</div>
<div class="moz-cite-prefix"><br>
</div>
<div class="moz-cite-prefix">The second case is very much like a
tabbed display where the some number of tabs are all shown in a
single display separated by 3D virtual space. In this case it is
the responsibility of the application to maintain separation
between the various content. <br>
</div>
<div class="moz-cite-prefix"><br>
</div>
<div class="moz-cite-prefix">All of the discussions I have heard
from multiple sources indicate that the browser and/or underlying
libraries would actively prevent the first case (single 3D web
page opening up multiple 2D pages). The security considerations
are too great and expecting the browser to manage all of the
interfaces is too difficult at this time.</div>
<div class="moz-cite-prefix"><br>
</div>
<div class="moz-cite-prefix">If you are developing your own
application for a 3D display that does this, then the
responsibility is now on you to ensure that there is no cross-site
information transfer. In this case, you would need to figure out
what happens to a web page that wished to use some resource of the
device (e.g., WebGL with canvas, or device camera) and how that
interacts with other demands for those same resources. For
example, imagine three different web pages, one was displaying a
virtual world with audio (all computer generated), one was using
the device camera for remote viewing, and one was an AR (camera +
computer generated) experience.</div>
<div class="moz-cite-prefix"><br>
</div>
<div class="moz-cite-prefix">If your intent is to use multiple pages
from a single site, then you do not have that issue; as it is
assumed that the a single person/organization has control and
access to all of that information. You could have a general page
for 3D content that also loads and positions various 2D pages
(like a list of participants or chat windows). The ability to
handle the interaction on the various 2D pages would be controlled
by the application providing the 3D environment context and the
browser.<br>
</div>
<div class="moz-cite-prefix"><br>
</div>
<div class="moz-cite-prefix">Leonard Daly</div>
<div class="moz-cite-prefix"><br>
</div>
<div class="moz-cite-prefix"><br>
</div>
<div class="moz-cite-prefix"><br>
</div>
<blockquote type="cite"
cite="mid:VI1PR0402MB348861506373D38C27BF64F6DABC0@VI1PR0402MB3488.eurprd04.prod.outlook.com">
<meta http-equiv="Content-Type" content="text/html;
charset=windows-1252">
<style type="text/css" style="display:none;"> P {margin-top:0;margin-bottom:0;} </style>
<div style="color: rgb(0, 0, 0); font-family:
Calibri,Helvetica,sans-serif; font-size: 12pt;">
<span>Thank you all for your answers. I appreciate that.</span></div>
<div style="color: rgb(0, 0, 0); font-family:
Calibri,Helvetica,sans-serif; font-size: 12pt;">
<span><br>
</span></div>
<div style="color: rgb(0, 0, 0); font-family:
Calibri,Helvetica,sans-serif; font-size: 12pt;">
<span>To avoid too much emphasis on the example given: the
broader question is about having the 3D web specification
prepared to support business-type processes for AR/VR devices.</span></div>
<div style="color: rgb(0, 0, 0); font-family:
Calibri,Helvetica,sans-serif; font-size: 12pt;">
<span><br>
</span></div>
<div style="color: rgb(0, 0, 0); font-family:
Calibri,Helvetica,sans-serif; font-size: 12pt;">
<span>It seems to me the most natural view is to see 2D webpages
as special cases of the 3D web, where all elements are
flattened to one plane. So in 3D space one should be able to
position and use both the active elements like textareas,
checkboxes etc, and more or less passive elements like div's
anywhere within the scene (Leonard, your first case scenario).
This of course includes combinations of these elements on flat
plains up to full 2D pages viewable in 3D.</span></div>
<div style="color: rgb(0, 0, 0); font-family:
Calibri,Helvetica,sans-serif; font-size: 12pt;">
<span><br>
</span></div>
<div style="color: rgb(0, 0, 0); font-family:
Calibri,Helvetica,sans-serif; font-size: 12pt;">
<span>Currently the resolutions for devices like HoloLens and I
think also Magic Leap (didn't try ML yet) are good enough for
viewing 2D web pages floating in 3D. This would allow
companies to easily extend their websites for 3D access by
using X3D, and/or an equivalent declarative syntax, in
combination with their existing 2D content.</span></div>
<div style="color: rgb(0, 0, 0); font-family:
Calibri,Helvetica,sans-serif; font-size: 12pt;">
<span><br>
</span></div>
<div style="color: rgb(0, 0, 0); font-family:
Calibri,Helvetica,sans-serif; font-size: 12pt;">
Albert Jan Wonnink</div>
</blockquote>
<br>
<div class="moz-signature">-- <br>
<font class="tahoma,arial,helvetica san serif" color="#333366">
<font size="+1"><b>Leonard Daly</b></font><br>
3D Systems & Cloud Consultant<br>
LA ACM SIGGRAPH Past Chair<br>
President, Daly Realism - <i>Creating the Future</i>
</font></div>
</body>
</html>