[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Bug-gnuzilla] GNU LibreJS won't be removed from GNU IceCat

From: Adonay Felipe Nogueira
Subject: Re: [Bug-gnuzilla] GNU LibreJS won't be removed from GNU IceCat
Date: Thu, 08 Mar 2018 09:57:45 -0300
User-agent: Gnus/5.13 (Gnus v5.13) Emacs/25.3 (gnu/linux)

> Regarding the scripting and general conception, I arrived at the impression 
> that the web is more or less an application stack (forms and JS and media 
> elements and whatnot) and not for mostly static documents at all, because 
> what do you have for the latter? Headers, paragraphs, lists and only the most 
> primitive type of link, that's basically it? The initial concept and spec 
> seems to be focused on providing a mechanism to link together resources from 
> different systems in different formats in lists, so it's easier to navigate 
> them while the host system details are abstracted away by the URL [1], while 
> the CERN research data and publications themselves weren't (re)written in 
> HTML (and how could they, who would ask the world to convert all of their 
> stuff for this small Hypertext system that doesn't offer a lot for text?). 
> Later, the browser people abandoned the semantic web as there's more money in 
> e-commerce, online applications and centralized services like Google. What 
> would happen if 

I would also like to add that HTML5 --- and even older versions perhaps
--- has forms.

Also --- no one mentioned this, so this is an addendum made by me ---,
if I recall correctly, with CSS event selectors one can use a dropdown
"nav" element --- or perhaps even "div" element, for older versions of
HTML --- without the need to use JavaScript.

Additionally --- another thing not mentioned, so another addendum ---, I
just tested another thing in Loïc "Magic Banana" Cerf's homepage at
UFMG: with plain HTML and CSS "clearfix", "auto margin", percentage
width and media queries, one can do mobile-first responsible design, all
without the need to use JavaScript.

As bill-auger said, I might be missing the essense of what Stephan
Kreutzer said, so please forgive me for making this possibly-useless
message. I didn't have time to see all the references yet.

With all that said, this message is just a brief summary of HTML+CSS

reply via email to

[Prev in Thread] Current Thread [Next in Thread]