I'm OK with that.
Looking at the naming of other specs we have names such as "CSSOM
Views" maybe we should use something along the lines of "Widgets
Views: Media Feature"? Just a thought though
Cheers,
Kenneth
On Tue, May 18, 2010 at 5:45 AM, Marcos Caceres wrote:
> Hi,
>
> Can we please rename
19:53:52 +0200, Kenneth Christiansen
> wrote:
>
>> Ola Joao,
>>
>> That would mean that the user would have to manually call all
>> matchMedium queries the user is interested in to find out which one
>> changed, without us being able to optimize this by not re
wrote:
> On Mon, 10 May 2010 19:44:37 +0200, Kenneth Christiansen
> wrote:
>
>> Hi Simon,
>>
>> So what you are suggesting is a kind of
>> document.addMediaRuleListener(mediaquery, listener) etc? I think that
>> should be quite easy to implement.
>>
Hi Simon,
So what you are suggesting is a kind of
document.addMediaRuleListener(mediaquery, listener) etc? I think that
should be quite easy to implement.
Kenneth
On Mon, May 10, 2010 at 2:27 PM, Simon Fraser wrote:
> On May 10, 2010, at 8:48 AM, L. David Baron wrote:
>
>> On Friday 2010-05-07
I wonder if it makes sense to have another method for adding the
listener instead of "abusing" the already existing matchMedium. For
instance, calling matchMedium is going to evaluate the expression,
which is not really necessary.
Kenneth
On Mon, May 10, 2010 at 12:48 PM, L. David Baron wrote:
>
Hi there,
This is a comment for the 20-Apr-2010 LCWD of the VMMF spec.
I would like the spec to clarify whether the view modes are mutual
exclusive or not. That is currently not clear. Can I have a view mode
of "windowed" and "maximized" at the same time? I guess the idea is
that they are all mut
Oi Marcos,
> # 3.2. Media Type Changed Event Types
> styleMedia.matchMedium("screen", function() { alert("no longer screen!") })
So you want it to call back when the match is no longer true? or did
you mean "not screen" ?
Kenneth
--
Kenneth Rohde Christiansen
Technical Lead / Senior Software E
Replying to myself.
Apparently I confused the chrome with the browser chrome, so sorry
about that. Maybe we could call it widget chrome to avoid confusion.
But this still leads me to one question. As the floating mode should
not show widget chrome, does that mean that it does not support
context
Maybe we could clear up the confusing simple by changing "Chrome - The
chrome comprises the visible parts of the user agent that do not
depend on the content (e.g. tool bars, title bars, menus)." to "Chrome
- The chrome comprises the visible parts of the user agent that do not
depend on the content
Hi there!
Here you have some of my comments on the current view mode spec, which
I have added support for in WebKit.
With regard to the media feature
> http://dev.w3.org/2006/waf/widgets-vmmf/
> http://www.w3.org/TR/widgets-vmmf/
I believe the 'all' is is not that useful as that is the same
Hi there,
The most important right now for Nokia at least would be to define the
view modes. The DOM events for changes to those can be handled later.
If you are doing a meeting about those, I would like to participate.
If we are not handling these soon, I'm afraid that we will probably
release p
Hi there,
The most important right now for Nokia at least would be to define the
view modes. The DOM events for changes to those can be handled later.
If you are doing a meeting about those, I would like to participate.
If we are not handling these soon, I'm afraid that we will probably
release p
12 matches
Mail list logo
