Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

<marquee> only fires start event when it's displayed #2957

Closed
ayg opened this issue Aug 22, 2017 · 5 comments · Fixed by #6343
Closed

<marquee> only fires start event when it's displayed #2957

ayg opened this issue Aug 22, 2017 · 5 comments · Fixed by #6343
Labels
interop Implementations are not interoperable with each other removal/deprecation Removing or deprecating a feature

Comments

@ayg
Copy link
Contributor

ayg commented Aug 22, 2017

When a marquee element is created, the user agent must queue a task to fire an event named start at the element.
https://html.spec.whatwg.org/#the-marquee-element

This doesn't match browser behavior (I intend to post tests today). Neither Edge nor Firefox fire the event until the element is added to a document. Edge also doesn't fire it for a marquee that's display: none, although Firefox does. I would say the spec should follow Edge, all else being equal, because they made up the feature.

(Chrome and WebKit do not implement marquee events AFAICT.)
@domenic
Copy link
Member

domenic commented Aug 22, 2017

If they do not implement marquee events, maybe we should just remove them instead?

@Yay295
Copy link
Contributor

Yay295 commented Aug 22, 2017

Since it's marked as obsolete, should we really be changing anything about its specification?

@annevk
Copy link
Member

annevk commented Aug 22, 2017

@Yay295 browsers are still required to support it (due to content using it) so therefore the specification needs to be accurate.

@ayg
Copy link
Contributor Author

ayg commented Aug 22, 2017

I have no objection to getting rid of these, assuming Gecko is willing to drop support. I filed a bug to add use counters: https://bugzilla.mozilla.org/show_bug.cgi?id=1392710

There's a Chromium bug to support marquee events that's closed as wontfix: https://bugs.chromium.org/p/chromium/issues/detail?id=522326

ayg added a commit to ayg/web-platform-tests that referenced this issue Aug 22, 2017
@ayg
Tests for marquee
f3a84b1 
Incorporates whatwg/html#2957 (assuming we take Edge's behavior).
ayg added a commit to ayg/web-platform-tests that referenced this issue Aug 22, 2017
@ayg
Improve marquee event tests
dac1e4d 
Incorporates whatwg/html#2957 (assuming we take Edge's behavior).
@ayg ayg mentioned this issue Aug 22, 2017
Open
@ayg
Copy link
Contributor Author

ayg commented Aug 22, 2017

I submitted a patch on the Mozilla bug to add use counters, although I won't be able to follow up on it unless I find someone to continue to employ me to work on web standards.

@annevk annevk added removal/deprecation Removing or deprecating a feature interop Implementations are not interoperable with each other labels Jan 22, 2018
domenic added a commit that referenced this issue Jan 29, 2021
@domenic
Remove <marquee> events
115645f 
They were only supported by one engine (Gecko).

Closes #2957.
@domenic domenic mentioned this issue Jan 29, 2021
Merged
3 tasks
domenic added a commit that referenced this issue Jan 29, 2021
@domenic
Remove <marquee> events
cd8e5c1 
They are only supported by one engine (Gecko).

Closes #2957.
imhele added a commit to imhele/html that referenced this issue Feb 18, 2021
@imhele @domfarolino
@annevk @domenic @emilio @momdo @jakearchibald @yutakahirano @syg @Kaiido @antosart @sideshowbarker @eltociear @carlosjoan91 @saschanaz @zcorpan
Merge/upstream (#5)
d121d02 
* Editorial: remove redundant "the"

* Meta: default branch rename

Also correct a broken link. Not even w3.org URLs are that cool.

Helps with whatwg/meta#174.

* Editorial: clean up calls to "parse a URL"

It actually takes a string, so calls should be clear about that.

* Review Draft Publication: January 2021

* Simplify <link>s

In particular, remove their activation behavior, stop them from matching
:link and :visited, and stop suggesting that they be focusable areas.

This also includes a slight expansion and rearrangement of the link
element's section to make it clearer what hyperlinks created by <link>
are meant for, contrasting them to <a> and <area> hyperlinks.

Closes whatwg#4831. Closes whatwg#2617. Helps with whatwg#5490.

* Meta: remove demos/offline/* (whatwg#6307)

These are no longer needed as of e4330d5.

* Meta: minor references cleanup

Use more HTTPS and drop obsolete HTML Differences reference.

* Editorial: anticlockwise → counterclockwise

We use en-US these days. Spotted in https://twitter.com/iso2022jp/status/1352601086519955456.

* Use :focus-visible in the UA stylesheet

See w3c/csswg-drafts#4278.

* Editorial: align with WebIDL and Infra

* Fix "update a style block" early return

The new version matches implementation reality and CSSWG resolution.

The algorithm was also inconsistent, as it looked at whether
the element was in a shadow tree or in the document tree, but it was
only specified to be re-run if the element becomes connected or
disconnected.

The CSSWG discussed this in
w3c/csswg-drafts#3096 (comment)
and http://wpt.live/shadow-dom/ShadowRoot-interface.html tests this.

This also matches closer the definition of <link rel="stylesheet">,
which does use connectedness (though it uses "browsing-context
connected", which is a bit different):
https://html.spec.whatwg.org/#link-type-stylesheet

* Modernize and refactor simple dialogs

This contains a small bug fix, in that confirm() and prompt() said
"return" in some cases instead of "return false" or "return null" as
appropriate.

Other notable changes, all editorial, are:

* Factoring out repeated "cannot show simple dialogs" steps, which will
  likely expand over time (see e.g. whatwg#6297).
* Separating out and explaining the no-argument overload of alert().
* Passing the document through to the "printing steps", instead of just
  having them talk about "this Window object".

* Meta: add definition markup for MessageEvent

* Remove <marquee> events

They are only supported by one engine (Gecko).

Closes whatwg#2957.

* Clarify when microtasks happen

* Ignore COEP on non-secure contexts

Fixes whatwg#6328.

* Editorial: update URL Standard integration

* Editorial: only invoke response's location URL once

Complements whatwg/fetch#1149.

* Track the incumbent settings and active script in Promise callbacks

Closes whatwg#5213.

* createImageBitmap(): stop clipping sourceRect to source's dimensions

It has been found in whatwg#6306 that this was an oversight at the time of its introduction. Current behavior goes against author expectations and no implementer has opposed the change to "no-clip".

Tests: web-platform-tests/wpt#27040.

Closes whatwg#6306.

* Remove CSP plugin-types blocking

With Flash not being supported anymore, the CSP directive plugin-types has lost its main reason for being and is being removed from the Content Security Policy specification: w3c/webappsec-csp#456.

This change removes references to the relevant algorithm from the Content Security Policy spec.

* Meta: set more dfn types

A follow-up to:

* whatwg#5694
* whatwg#5916

* Editorial: occuring → occurring

* Make all plugin-related APIs no-ops

Part of whatwg#6003.

* Disallow simple dialogs from different-origin domain iframes

Closes whatwg#5407.

* Revive @@iterator for PluginArray/MimeTypeArray/Plugin

@@iterator is implicitly installed by defining an indexed property getter. Since there is no other way to define it exclusively, this restores some methods back to being indexed getters.

This fixes an inadvertent observable behavior change in d4f07b8.

* Adjust web+ scheme security considerations to account for FTP removal

Also, network scheme is now reduced to HTTP(S) scheme.

Helps with whatwg#5375, but form submission issue remains.

See whatwg/fetch#1166 for context.

* Meta: export pause

Nobody but XMLHttpRequest take a dependency on this please. You have been warned.

Context: whatwg/xhr#311.

* Fix typo: ancestor → accessor

Fixes whatwg#6374.

Co-authored-by: Dominic Farolino <domfarolino@gmail.com>
Co-authored-by: Anne van Kesteren <annevk@annevk.nl>
Co-authored-by: Domenic Denicola <d@domenic.me>
Co-authored-by: Emilio Cobos Álvarez <emilio@crisal.io>
Co-authored-by: Momdo Nakamura <xmomdo@gmail.com>
Co-authored-by: Jake Archibald <jaffathecake@gmail.com>
Co-authored-by: Yutaka Hirano <yhirano@chromium.org>
Co-authored-by: Shu-yu Guo <syg@chromium.org>
Co-authored-by: Kaiido <tristan.fraipont@gmail.com>
Co-authored-by: Antonio Sartori <anton.sartori@gmail.com>
Co-authored-by: Michael[tm] Smith <mike@w3.org>
Co-authored-by: Ikko Ashimine <eltociear@gmail.com>
Co-authored-by: Carlos IL <carlosjoan91@gmail.com>
Co-authored-by: Kagami Sascha Rosylight <saschanaz@outlook.com>
Co-authored-by: Simon Pieters <zcorpan@gmail.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
interop Implementations are not interoperable with each other removal/deprecation Removing or deprecating a feature
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Remove <marquee> events whatwg/html
5 participants
@domenic @ayg @annevk @Yay295 and others