- From: Jonas Sicking <jonas@sicking.cc>
- Date: Wed, 13 Aug 2014 23:43:02 -0700
- To: Lars Knudsen <larsgk@gmail.com>
- Cc: public-webapps <public-webapps@w3.org>
Yup. Well.. sounds like people, including you, pointed out these
problems. No idea why it was ignored since I wasn't there.
/ Jonas
On Wed, Aug 13, 2014 at 11:28 PM, Lars Knudsen <larsgk@gmail.com> wrote:
> If only someone had pointed out these problems earlier ;)
>
> On Aug 5, 2014 11:17 PM, "Jonas Sicking" <jonas@sicking.cc> wrote:
>>
>> Hi All,
>>
>> I think the current interaction between the screen orientation and
>> device orientation specs is really unfortunate.
>>
>> Any time that you use the device orientation in order to render
>> something on screen, you have to do non-obvious math in order to get
>> coordinates which are usable. Same thing if you want to use the device
>> orientation events as input for objects which are rendered on screen.
>>
>> I would argue that these are the by far most common use cases for
>>
>> I agree that the main problem here is that the deviceorientation spec
>> defined that their events should be relative to the device rather than
>> to the screen. However we can still fix the problem by simply adding
>>
>> partial interface DeviceOrientationEvent
>> {
>> readonly attribute double? screenAlpha;
>> readonly attribute double? screenBeta;
>> readonly attribute double? screenGamma;
>> }
>>
>> No new events needs to be defined.
>>
>> I guess we can argue that this should be added to the
>> DeviceOrientation spec, but that seems unlikely to happen in practice
>> anytime soon. I think we would do developers a disservice by blaming
>> procedural issues rather than trying to solve the problem.
>>
>> I think mozilla would be happy to implement such an addition to the
>> DeviceOrientation event (I'm currently checking to make sure). Are
>> there other UAs that have opinions (positive or negative) to such an
>> addition?
>>
>> / Jonas
>>
>
Received on Thursday, 14 August 2014 06:44:05 UTC