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

HTML Tag not support! #1382

Closed
QuestionPython opened this issue Jan 7, 2018 · 5 comments
Closed

HTML Tag not support! #1382

QuestionPython opened this issue Jan 7, 2018 · 5 comments

Comments

@QuestionPython
Copy link

QuestionPython commented Jan 7, 2018 •
edited
Loading

Example : marquee Tag(sublimehq/sublime_text#2153)

https://developer.mozilla.org/en-US/docs/Web/HTML/Element/marquee

<marquee bgcolor="yellow" behavior="alternate">
	IN THE NAME OF GOD!
</marquee>

More Sample:

<marquee>This text will scroll from right to left</marquee>

<marquee direction="up">This text will scroll from bottom to top</marquee>

<marquee direction="down" width="250" height="200" behavior="alternate" style="border:solid">
  <marquee behavior="alternate">
    This text will bounce
  </marquee>
</marquee>
@FichteFoll
Copy link
Collaborator

What do you mean with "not supported"? Where is this not supported? What should it do and what is it actually doing?

@FichteFoll FichteFoll mentioned this issue Jan 7, 2018
Closed
@QuestionPython
Copy link
Author

not supported mean , not suggest in auto-complate editor. @FichteFoll

@FichteFoll
Copy link
Collaborator

As indicated by the MDN reference in OP, the tag is long deprecated and not to be used anymore. It is not sensical to suggest using it in a completion.

You can add a snippet locally if you really need to, but this isn't something that every ST user should be bothered with.

@kleinfreund
Copy link
Contributor

I think this can be closed, no?

deathaxe pushed a commit to deathaxe/sublime-packages that referenced this issue Aug 25, 2019
[GitHub] Close obsolete issues
f2f95c2 
This PR proposes to close some already fixed issues, which were not (correctly) referenced in the fixing pull requests.

Closes sublimehq#442
Closes sublimehq#685
Closes sublimehq#691 (invalid)
Closes sublimehq#795
Closes sublimehq#807
Closes sublimehq#903
Closes sublimehq#1141
Closes sublimehq#1172
Closes sublimehq#1245
Closes sublimehq#1257
Closes sublimehq#1286
Closes sublimehq#1320
Closes sublimehq#1357
Closes sublimehq#1382 (wontfix)
Closes sublimehq#1403
Closes sublimehq#1451
Closes sublimehq#1453 (maybe)
Closes sublimehq#1472
Closes sublimehq#1495
Closes sublimehq#1540
Closes sublimehq#1542
Closes sublimehq#1565
Closes sublimehq#1576
Closes sublimehq#1625
Closes sublimehq#1880
Closes sublimehq#1898
Closes sublimehq#1940 (invalid)
@deathaxe deathaxe mentioned this issue Sep 7, 2019
Closed
@wbond
Copy link
Member

wbond commented Oct 24, 2019

This issue is being closed since the tag is deprecated, and thus we don't want to suggest it to users.

@wbond wbond closed this as completed Oct 24, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
4 participants
@wbond @FichteFoll @kleinfreund @QuestionPython