[ViewModes] Proposal: split the specification, add new events

Hi All,

Attached you can find the summary of the media features, as specified in [1] and [2].

Within this mail I would like to raise/discuss two points:

a) architecturally inconsistent handling of media features and their related APIs/events per spec

b) propose new events


Ad a)

There seems to be architectural inconsistency regarding what is specified where.
The basic media features are listed in [1], additional "view-mode" media feature is specified in [2], and the APIs/events related to all of those media features are to be specified in [2].
I think we could fix it before it is too late.

My proposal is:

1. Let [2] specify only "view-mode" media feature.

2. Move the scripting interfaces from [2] to some new spec.

3. I could prepare the split.


Ad b)

As listed in the attached document the orientation and aspect-ratio media features do not depend on the device and may change dynamically. So I would like to propose the following:

1. Add OrientationChangeEvent

2. Add AspectRatioChangeEvent

If the split of the specification would be (widely) accepted, these additions would go to the new spec (titled e.g. "Media Queries: API & Events", as originally proposed).

Please let me know what you think.

Thanks.

Kind regards,
Marcin

[1] http://www.w3.org/TR/css3-mediaqueries/
[2] http://dev.w3.org/2006/waf/widgets-vm/Overview.src.html


Marcin Hanclik
ACCESS Systems Germany GmbH
Tel: +49-208-8290-6452  |  Fax: +49-208-8290-6465
Mobile: +49-163-8290-646
E-Mail: marcin.hanclik@access-company.com


________________________________________

Access Systems Germany GmbH
Essener Strasse 5  |  D-46047 Oberhausen
HRB 13548 Amtsgericht Duisburg
Geschaeftsfuehrer: Michel Piquemal, Tomonori Watanabe, Yusuke Kanda

www.access-company.com

CONFIDENTIALITY NOTICE
This e-mail and any attachments hereto may contain information that is privileged or confidential, and is intended for use only by the
individual or entity to which it is addressed. Any disclosure, copying or distribution of the information by anyone else is strictly prohibited.
If you have received this document in error, please notify us promptly by responding to this e-mail. Thank you.