On Wed, Jan 15, 2014 at 02:53:00PM -0200, Jesus Sanchez-Palencia wrote:
> The only idea we had was to change a bit how the JS shim is
> implemented. I would do something like:
>
> "
> var orientationValue = "";
>
> Object.defineProperty(window.screen, "orientation", {
> configurable: false,
>
Hey,
On Wed, Jan 15, 2014 at 2:57 PM, Kenneth Rohde Christiansen
wrote:
> That was what I wanted to avoid :-) ie. when accessing, I wanted to
> check if it had been set (there is a good chance it has) and if not do
> a sync call.
>
> The other option would be if there is a way to send the orien
That was what I wanted to avoid :-) ie. when accessing, I wanted to
check if it had been set (there is a good chance it has) and if not do
a sync call.
The other option would be if there is a way to send the orientation to
the JS from within the *Instance ctor, as I suppose the ctor will have
to b
Hi,
I'm replying, but please keep in mind I haven't read the W3C API spec
for Screen Orientation.
On Wed, Jan 15, 2014 at 2:17 PM, Kenneth Rohde Christiansen
wrote:
> Hi there,
>
> The orientation extension has the issues that the values might not be
> set by the extension before they are access
Hi there,
The orientation extension has the issues that the values might not be
set by the extension before they are accessed. I discussed this with
Jeez and he suggested that we just always load the extension.
Thus we could load the extension possible just after creating the
document (DOM readyS
