Hi Robin, Good point!
In the email and attachment starting this thread I included the comment that AspectRatioChangeEvent could be realized with ResolutionChangeEvent. With your comment the question is whether we need ResolutionChangeEvent if we already have onresize. We have change from pull model (onresize is invoked, but the resolution has to be fetched separately) to push model (new dimensions are in the event). Do we need ResolutionChangeEvent then? Any opinion? Thanks, Marcin Marcin Hanclik ACCESS Systems Germany GmbH Tel: +49-208-8290-6452 | Fax: +49-208-8290-6465 Mobile: +49-163-8290-646 E-Mail: [email protected] -----Original Message----- From: Robin Berjon [mailto:[email protected]] Sent: Monday, August 24, 2009 12:40 PM To: Marcin Hanclik Cc: [email protected] Subject: Re: [ViewModes] Proposal: split the specification, add new events Hi, On Aug 20, 2009, at 13:55 , Marcin Hanclik wrote: > My proposal is: > > 1. Let [2] specify only "view-mode" media feature. I think that's a good idea. > 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 I think that these are useful events, but I'd like to make sure we're not duplicating existing stuff. Notably, how is AspectRatioChangeEvent different from onresize? -- Robin Berjon - http://berjon.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.
