Re: Question / Request for HTML or CSS

Allen,

I believe the standards only define what user agents *must* implement to be
compliant with the specification, not what they *must not* implement.  For
example, a user agent customized by a sales kiosk corporation *may* implement
a deprecated HTML element in order to standardize marquee scrolling across
all of their kiosk locations.  Browser vendors implement custom elements
and property prefixes *in addition to* what the standard defines.

The <marquee> element defines a stylistic behavior without adding any
semantic markup that a header element would not add to the same content.
 As you say, scrolling behavior and readability is the responsibility of
the designer.  It is much easier to make accommodations for fixing such
designs when sticking to the more modularized styling and scripting
standards that are now defined.

--Xaxio




On Sat, Mar 30, 2013 at 9:57 AM, Allen Flick <allenflick@gmail.com> wrote:

> Didn't know we pions out here could make suggestions to the powers that be.
>
> I've been piddling with my high school class reunion site for years now.
> And have
> just now discovered that one of my favorite HTML elements may go away at
> some
> undefined time in the future, and I'd like to see it become part of the
> "standard"
> even though it's now used by 1005 of the users out there in the internet
> world.
>
> <marquee>scrolling text</marquee>  or
> <marquee>(scrolling images)</marquee>  is what I'm talking about. Although
> whatever
> is scrolling and maybe a little difficult to read, that's the
> responsibility of the web
> designer, right?  Some say that the designer should not put things like
> that on their
> sites, but then turn around and tell you that it can be done using CSS3.
>
> Maybe it should be a CSS provision, but in actually setting a standard for
> this should
> not make the implementation any more difficult than the way it is
> currently.
>
> The silliest thing you can do, as the authority on web standards, is leave
> <marquee>
> scrolling text</marquee> the way it is ..... totally in limbo, letting
> each browser decide
> to implement it or not.  ---> On my class site there are several
> <marquee>'s but the
> latest one I put in uses images. I was immediately notified by someone
> with Chrome
> on a Mac that the new <marquee> spreads across the entire screen,
> distorting the
> entire display.
>
> I'd say to either have it in the standard to be supported, or if not in
> the standard, it
> should be standard NOT to support it.
>
> Just MHO !!
>
>
>
>