- From: Marcos Caceres <marcosc@opera.com>
- Date: Wed, 23 Sep 2009 19:15:03 +0300
- To: Marcin Hanclik <Marcin.Hanclik@access-company.com>
- Cc: Arthur Barstow <art.barstow@nokia.com>, public-webapps <public-webapps@w3.org>
On Wed, Sep 23, 2009 at 4:36 PM, Marcin Hanclik <Marcin.Hanclik@access-company.com> wrote: > Hi, > > One more comment to the below: > There is one use case not handled by the below scenarios: > In case the width/height are dropped on the Widget interface, the widget would not know the initial dimensions. > E.g. in Win32 each new window get WM_SIZE event with the initial width/height. > However, I am not sure whether we should mandate the ResolutionChangedEvent to be used for the initial viewport size. > > So I would opt for keeping the ResolutionChangedEvent, dropping width/height on the ResolutionChangedEvent, and keeping width/height in the Widget interface. > I'm still confused as to why we can't keep both. Is it because of redundancy? -- Marcos Caceres http://datadriven.com.au
Received on Wednesday, 23 September 2009 16:16:04 UTC