Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > comp.lang.javascript > #26014

Re: DOM style object property names with vendor prefixes

From "Chris Beall" <Chris_Beall@prodigy.net>
Newsgroups comp.lang.javascript
Subject Re: DOM style object property names with vendor prefixes
Date 2014-10-28 17:56 -0400
Organization A noiseless patient Spider
Message-ID <op.xogm79m5tnmj2w@cbealls-imac.local> (permalink)
References (1 earlier) <83210457.YLdJyC3XC5@PointedEars.de> <op.xoes9kehtnmj2w@cbealls-imac.local> <2636975.CJeWhIb7Se@PointedEars.de> <op.xoez15kttnmj2w@cbealls-imac.local> <2808896.X0fOSNMZzN@PointedEars.de>

Show all headers | View raw


Thomas 'PointedEars' Lahn wrote:

> Chris Beall wrote:
(snip)
> Do you mean inheritance of style property declarations?

Yes.

>>   - if you guess wrong about what things will forever be styled in the
>>   same way, you later have to go back and separate out the style for the
>> different elements.  Having guessed wrong on several occasions, I tend  
>> to
>> keep them separate to begin with.
>
> Yes, the better solution requires more thinking in advance.

I will agree with 'better under certain circumstances'.  I suspect you  
encounter those circumstances more often than I do.  Fair enough.

>>   - (specific to me) The various browsers construct the DOM tree
>> differently in some cases,
>
> That would be surprising.  With *Valid* markup, I have, to my knowledge,
> never gotten different document trees in 14 years of professional Web
> development.  Have you used <http://validator.w3.org/>?

Often.  Sometimes not often enough.  And things change over time, but I  
have seen:
- If a CSS selector uses multiple class names, IE reverses their order in  
the DOM selectorText.
So if the CSS selector is .foo.bar, an attempt to find it in the DOM  
selectorText will fail, unless you search for .bar.foo
And I have been told (http://www.quirksmode.org/dom/changess.html#link4),  
but did not extensively research,
that some more complex selectors, such as groups, may be split into  
multiple rules within 'your browser', which I interpreted to mean 'the DOM  
as built by your browser'.

>> one of them being the use of selector grouping.

> Meaning?

a comma-separated list of selectors that share the same declarations.
http://www.w3.org/TR/CSS21/selector.html#grouping

>> That would confuse the function I use to modify the stylesheet, so I  
>> don't
>> do that.
>
> That is a circular reasoning, is it not?  You only have those problems in
> the first place *because* you have been using the equivalent of inline  
> style
> declarations instead of style*sheets*.

Hmmm, seems linear to me.  I chose to go down a certain path (which is not  
the one that you prefer) and I'm sticking with it.  There are always  
consequences, but these are MY consequences.

(snip interesting but no longer relevant.  See way below.)
>
> We have different approaches at filtering.

Both valid.  I'll study yours further, but it is unrelated to this thread.

(snip)
>> which isn't quite what I meant by 'hiding'.  So I really need to change
>> only one property, display.
>
> That depends on whether you want a smooth transition, improving the user
> experience, or not:

This would lead us into philosophy of the user experience.  In this case I  
believe the user wants an instant response, not artistry.  I have used  
smooth transitions elsewhere, to good (IMO) effect.  I feel they are  
almost never a good idea except in response to a user action (although my  
current issue is related to just such an exception...)

> <http://www.nngroup.com/articles/animation-usability/>

Looks thoughtful.  I've bookmarked it.

>>> You could then even use, e.g., LESS

Suggestion: When using an acronym for the first time, spell it out in  
full, followed by the acronym within parentheses.  I interpreted this as a  
word, uppercased for emphasis, and hence did not understand the subsequent  
syntax.

(snip)
> I wondered which properties, whose value did not change, you have
> attempted to change and how.  (Which browser is secondary, and with  
> prefixed
> properties the targeted layout engine can be inferred from the property
> name.)

animation_duration
and it turns out the change was being made, but not acted upon as I  
expected (more below)

> Please read the FAQ on quoting.

I'm familiar with the guidelines.  It is sometimes difficult to determine  
what of the foregoing discussion remains relevant.  I've tried to be more  
parsimonious this time.

CHANGE OF DIRECTION

As a result of testing, I have determined that I am, in fact, able to  
modify animation_duration within a specific CSS directive, so this topic  
is logically closed.  I was misinterpreting the reason for my symptom.

BUT, the modification, driven by <body onload=...>, does not take effect  
on the page as initially displayed, except in Firefox.  I will open a new  
thread shortly, with a live testcase.  The issue now seems to be related  
to the timing environment within which JavaScript executes, rather than  
anything in the language itself, but we shall see.

I do appreciate the responses to date.

Chris Beall

Back to comp.lang.javascript | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread


Thread

DOM style object property names with vendor prefixes "Chris Beall" <Chris_Beall@prodigy.net> - 2014-10-27 16:30 -0400
  Re: DOM style object property names with vendor prefixes "Michael Haufe (TNO)" <tno@thenewobjective.com> - 2014-10-27 14:07 -0700
    Re: DOM style object property names with vendor prefixes "Chris Beall" <Chris_Beall@prodigy.net> - 2014-10-27 17:43 -0400
    Re: DOM style object property names with vendor prefixes Andrew Poulos <ap_prog@hotmail.com> - 2014-10-28 09:48 +1100
      Re: DOM style object property names with vendor prefixes "Michael Haufe (TNO)" <tno@thenewobjective.com> - 2014-10-27 22:45 -0700
        Re: DOM style object property names with vendor prefixes Andrew Poulos <ap_prog@hotmail.com> - 2014-10-28 19:31 +1100
          Re: DOM style object property names with vendor prefixes "Chris Beall" <Chris_Beall@prodigy.net> - 2014-10-28 09:59 -0400
          Re: DOM style object property names with vendor prefixes Thomas 'PointedEars' Lahn <PointedEars@web.de> - 2014-10-28 15:26 +0100
          Re: DOM style object property names with vendor prefixes Andrew Poulos <ap_prog@hotmail.com> - 2014-10-31 12:29 +1100
  Re: DOM style object property names with vendor prefixes Thomas 'PointedEars' Lahn <PointedEars@web.de> - 2014-10-27 22:20 +0100
    Re: DOM style object property names with vendor prefixes "Chris Beall" <Chris_Beall@prodigy.net> - 2014-10-27 18:11 -0400
      Re: DOM style object property names with vendor prefixes Thomas 'PointedEars' Lahn <PointedEars@web.de> - 2014-10-27 23:45 +0100
        Re: DOM style object property names with vendor prefixes "Chris Beall" <Chris_Beall@prodigy.net> - 2014-10-27 20:38 -0400
          Re: DOM style object property names with vendor prefixes Thomas 'PointedEars' Lahn <PointedEars@web.de> - 2014-10-28 19:49 +0100
            Re: DOM style object property names with vendor prefixes "Chris Beall" <Chris_Beall@prodigy.net> - 2014-10-28 17:56 -0400
              Re: DOM style object property names with vendor prefixes Thomas 'PointedEars' Lahn <PointedEars@web.de> - 2014-10-29 21:07 +0100
                Re: DOM style object property names with vendor prefixes "Chris Beall" <Chris_Beall@prodigy.net> - 2014-10-30 12:50 -0400
                Re: DOM style object property names with vendor prefixes Thomas 'PointedEars' Lahn <PointedEars@web.de> - 2014-10-30 19:13 +0100
                Re: DOM style object property names with vendor prefixes "Chris Beall" <Chris_Beall@prodigy.net> - 2014-10-30 17:17 -0400
                Re: DOM style object property names with vendor prefixes Thomas 'PointedEars' Lahn <PointedEars@web.de> - 2014-10-31 20:35 +0100
        Re: DOM style object property names with vendor prefixes "Chris Beall" <Chris_Beall@prodigy.net> - 2014-10-27 23:19 -0400
          Re: DOM style object property names with vendor prefixes John Harris <niam@jghnorth.org.uk.invalid> - 2014-10-28 10:11 +0000
            Re: DOM style object property names with vendor prefixes Tim Streater <timstreater@greenbee.net> - 2014-10-28 11:42 +0000
              Re: DOM style object property names with vendor prefixes "Chris Beall" <Chris_Beall@prodigy.net> - 2014-10-28 09:52 -0400
            Re: DOM style object property names with vendor prefixes "Chris Beall" <Chris_Beall@prodigy.net> - 2014-10-28 09:49 -0400
              Re: DOM style object property names with vendor prefixes John Harris <niam@jghnorth.org.uk.invalid> - 2014-10-29 15:48 +0000
          Re: DOM style object property names with vendor prefixes Thomas 'PointedEars' Lahn <PointedEars@web.de> - 2014-10-28 15:54 +0100
        Re: DOM style object property names with vendor prefixes Scott Sauyet <scott.sauyet@gmail.com> - 2014-10-30 08:12 -0700
  Re: DOM style object property names with vendor prefixes Joao Rodrigues <groups_jr-1@yahoo.com.br> - 2014-10-29 15:23 -0200
    Re: DOM style object property names with vendor prefixes Thomas 'PointedEars' Lahn <PointedEars@web.de> - 2014-10-29 21:47 +0100
      Re: DOM style object property names with vendor prefixes Thomas 'PointedEars' Lahn <PointedEars@web.de> - 2014-10-30 07:32 +0100
    Re: DOM style object property names with vendor prefixes "Chris Beall" <Chris_Beall@prodigy.net> - 2014-10-30 10:47 -0400

csiph-web