|
|
Posted by Spartanicus on 10/10/82 11:48
Michael Winter <m.winter@blueyonder.co.uk> wrote:
>> This works when the viewport width is changed up or down by dragging the
>> right viewport border, but not when a non maximised MDI window is
>> maximised using the window button, it does work when an MDI window is
>> "unmaximized". It works when I close Opera's side panel, but not when I
>> open the panel.
>
>Are you absolutely certain of that? I'll admit that I didn't test it
>because I forgot that Opera has independent child windows (I always have
>them maximised, including pop-ups), but both 7.03 and 8.54 (I didn't
>check intervening versions) fire in response to all of those actions,
>here. I don't have v9.
I tried it with V7, V8 and V9, it behaves as I described on my system.
Here's a temporary copy containing the code, I don't think that I've
made mistakes in copying it:
http://homepage.ntlworld.com/spartanicus/temp.htm
I've replaced the reload with an alert dialog for testing.
>> I'm not aware of a spec requirement to reevaluate the CSS media query
>> upon a window resize, nor am I convinced that it should be.
>
>If a set of rules are applied only because certain circumstances dictate
>that they should be, it would seem logical to reconsider the application
>of those rules if the circumstances change. It doesn't make a great deal
>of sense to continue to apply rules to a document that is in a viewport
>say 50em wide, if it's now 30em wide and some other rule set is more
>appropriate.
But there are potentially a fair number of different things that media
queries could be used for, it could be neigh impossible for a browser to
determine what action to take depending on the significant number of
UI actions that a user may initiate. The author coding these functions
on the other hand knows what behaviour is needed, it seems reasonable to
me that the author should also implement the behaviour such as in this
case triggering a reload. After all, dynamic behaviour belongs in the
Javascript domain.
>> But the main obstacle for me to learn JavaScript is my dislike for what
>> is typically done with it (I have it disabled by default in my browser),
>> the rare good uses I see for it, which results in only an occasional
>> desire to use it.
>
>I can appreciate that, and I most definitely agree that a lot of its use
>is poor, and often unnecessary or inappropriate. But, I don't think it
>should stand in your way of learning the language.
>
>If you're in no hurry, you might be content to read and post to
>c.l.javascript. It is surely the best source of information you'll find
>anywhere[1]
I'd gladly agree with that, in the little time that I've spent in
c.l.javascript it was obvious to me that some of it's contributors are
highly skilled people.
The same is true for the areas that I do know something about. The
quality of information in virtually all books on these subjects is not
nearly as good as the information available from the best newsgroup
contributors.
--
Spartanicus
Navigation:
[Reply to this message]
|