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

Groups > comp.lang.javascript > #40175

Re: Browser-dependent JavaScript problem

Show key headers only | View raw

Here we go again… :-(

John Stockton wrote:

> On Monday, 24 May 2021 at 01:24:26 UTC+1, Thomas 'PointedEars' Lahn wrote
> (***) too much writing, with not enough thinking.

FOAD. 

>> “Internet Explorer 11 follows the OS component lifecycle,[7] which means
>> it remains supported with technical and security fixes while operating
>> systems including it as a component are shipped. This means that there is
>> no date for end of support for Internet Explorer 11.[8] On August 17,
>> 2020, Microsoft published a timeline indicating that the Microsoft Teams
>> product would stop supporting Internet Explorer 11 on November 30, 2020,
>> and Microsoft 365 products will end Internet Explorer 11 support on
>> August 17, 2021.[9]”
>> 
>> <https://en.wikipedia.org/wiki/Internet_Explorer_11>
> 
> (***) I have seen, somewhere, a recent authoritative statement which
> indicates much the same dates but about a year later.

Irrelevant unless there is evidence to support it.  Eyewitness accounts
are not considered evidence in (computer) science – something someone who is 
arrogant enough to post with their “Dr” in Usenet should be aware of.
 
>> Compare: <https://github.com/airbnb/javascript>
>> >> Any suggestions?
>> > 
>> > I don't think you can set an element's style the way you are doing it.
>> That is correct. “style” is historically a *read-only* *object*
>> property[1], and has been FOR 20 YEARS NOW [2].
>> 
>> Only as per the WHATWG DOM one may assign a string value to it, as a
>> shorthand.[3]
>> 
>> A backwards-compatible possibility would be to set the “style” attribute
>> to that primitive string value. But it is better to append a stylesheet,
>> and then format based on CSS class names.
> 
> That

Which of the THREE suggestions that I have made?

> had no effect - neither better nor worse.

Learn to read.  The effect that the latter has is to be backwards-
compatible, and that changes the code for the better.

“It works for me” is never a justification for a questionable practice.  
After more than two decades, haven’t we been over this /ad nauseam/ now?
 
> [Full quote]

FOAD.

>>---- EOF -----
> 
> (*** ...)
> 
> "Rem acu non tetigisti" - as PGW might have written, but apparently did
> not (though a very few others did).

FOAD.
 
> With the original code, most browsers tried would say something like
> //      Uncaught TypeError: Failed to execute 'appendChild' on
> //      'Node': parameter 1 is not of type 'Node'.
> //	  at Show_Age (inc-cmmn.js:60)
> //	  at fred-set.htm:17
> 
> from which I subsequently deduced that when createTextNode is fed with a
> non-string argument it (maybe an undefined one) returns a non-Node of
> disgust which fatally upsets appendChild.

PEBKAC.

> Progress has been made.

Evidently after 20 years you have not made any progress at all.  Neither in 
your coding nor in your personality development.  But I guess that’s too 
much to hope for at this point.
 
-- 
PointedEars
FAQ: <http://PointedEars.de/faq> | <http://PointedEars.de/es-matrix>
<https://github.com/PointedEars> | <http://PointedEars.de/wsvn/>
Twitter: @PointedEars2 | Please do not cc me./Bitte keine Kopien per E-Mail.

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

Thread

Re: Browser-dependent JavaScript problem Thomas 'PointedEars' Lahn <PointedEars@web.de> - 2021-05-24 02:24 +0200
  Re: Browser-dependent JavaScript problem John Stockton <dr.j.r.stockton@gmail.com> - 2021-05-28 15:36 -0700
    Re: Browser-dependent JavaScript problem John Stockton <dr.j.r.stockton@gmail.com> - 2021-05-29 13:24 -0700
    Re: Browser-dependent JavaScript problem Thomas 'PointedEars' Lahn <PointedEars@web.de> - 2021-06-07 03:05 +0200
      Re: Browser-dependent JavaScript problem "Mark-" <nospam@mapson.xyz> - 2021-06-07 02:13 +0000
        Re: Browser-dependent JavaScript problem Andrew Poulos <ap_prog@hotmail.com> - 2021-06-07 15:24 +1000
          Re: Browser-dependent JavaScript problem "Mark-" <nospam@mapson.xyz> - 2021-06-07 12:15 +0000
            Re: Browser-dependent JavaScript problem Andrew Poulos <ap_prog@hotmail.com> - 2021-06-08 07:35 +1000
              Re: Browser-dependent JavaScript problem "Mark-" <nospam@mapson.xyz> - 2021-06-08 12:33 +0000
                Re: Browser-dependent JavaScript problem Andrew Poulos <ap_prog@hotmail.com> - 2021-06-09 09:40 +1000
                Re: Browser-dependent JavaScript problem "Mark-" <nospam@mapson.xyz> - 2021-06-09 00:36 +0000
                Re: Browser-dependent JavaScript problem Andrew Poulos <ap_prog@hotmail.com> - 2021-06-09 13:14 +1000
                Re: Browser-dependent JavaScript problem "Mark-" <nospam@mapson.xyz> - 2021-06-09 03:27 +0000
                Re: Browser-dependent JavaScript problem Andrew Poulos <ap_prog@hotmail.com> - 2021-06-09 20:57 +1000
      Re: Browser-dependent JavaScript problem The Natural Philosopher <tnp@invalid.invalid> - 2021-06-07 07:52 +0100
      Re: Browser-dependent JavaScript problem John Harris <niam@jghnorth.org.uk.invalid> - 2021-06-07 18:18 +0100
    Re: Browser-dependent JavaScript problem Arno Welzel <usenet@arnowelzel.de> - 2021-06-07 09:56 +0200
  Re: Browser-dependent JavaScript problem Arno Welzel <usenet@arnowelzel.de> - 2021-05-31 07:30 +0200
    Re: Browser-dependent JavaScript problem JJ <jj4public@gmail.com> - 2021-06-01 18:40 +0700

csiph-web