1238322 - Document WebVTT's :current, :past, :future CSS pseudo-classes

Status: RESOLVED WONTFIX

(Developer Documentation Graveyard :: CSS, defect, P5)

Description

[Chris Rebert]

See https://drafts.csswg.org/selectors/#time-pseudos
These seem to be supported in at least Chrome and Safari.

Comment 1

[Chris Rebert]

See also https://w3c.github.io/webvtt/#the-past-and-future-pseudo-classes

Comment 2

[Shubham Rathore[:gabbar1947]]

Where exactly do I need to make the changes ? is it GIT?

Comment 3

[Chris Rebert]

When logged into MDN, you can visit these URLs to create the pages:
https://developer.mozilla.org/en-US/docs/Web/CSS/:past
https://developer.mozilla.org/en-US/docs/Web/CSS/:future
https://developer.mozilla.org/en-US/docs/Web/CSS/:current

Comment 4

[Benjamin De Brasi]

Hi, I'd like to take this bug.

Comment 5

[Ayus Das]

(In reply to Chris Rebert from comment #0)

See https://drafts.csswg.org/selectors/#time-pseudos
These seem to be supported in at least Chrome and Safari.

I want to contribute to this project.Can anyone please guide me to the contribution?

Comment 6

[shubham.gupta2956]

I want to contribute to this project. Please guide me about how to start working on this issue.

Comment 7

[Janet Swisher]

Chris: Can you (find someone to) guide shubman.gupta2956?

Comment 8

[Chris Mills [:cmills]]

I am happy to help with getting shubham.gupta2956 started.

First of all, do you have an MDN account? If not, create one and tell me what your username is so that I can give you page creation permissions.

After that, the next steps would be:

1. For each page, create a new page as a subpage of https://developer.mozilla.org/en-US/docs/Web/CSS
2. For the content of each page, use an existing page (such as https://developer.mozilla.org/en-US/docs/Web/CSS/:hover) as a template, copy the content, and change it to be appropriate for that pseudoclass.
3. Save those pages, and let me review them for you so I can suggest improvements.
4. Make sure the new pseudoclasses' compat data is recorded in https://github.com/mdn/browser-compat-data
5. Make sure the new pseudoclasses' formal syntax, etc. is recorded in https://github.com/mdn/data

Comment 9

[shubham.gupta2956]

Sorry for very late response @cmills.
My MDN account username is - shubhamgupta2956
I will start following steps you have mentioned. Thanks for helping me to get started.

Comment 10

[Chris Mills [:cmills]]

(In reply to shubham.gupta2956 from comment #9)

Sorry for very late response @cmills.
My MDN account username is - shubhamgupta2956
I will start following steps you have mentioned. Thanks for helping me to get started.

Hi there! I have given you the permissions you need to create the pages. Feel free to ask me for help if you have any questions, wat a review, etc. Thanks for the offer of help with this!

Comment 11

[shubham.gupta2956]

1. For each page, create a new page as a subpage of https://developer.mozilla.org/en-US/docs/Web/CSS
   cmills can you please elaborate this point a little. I am getting confused on this point. Thanks.

Comment 12

[Chris Mills [:cmills]]

For each page, create a new page as a subpage of https://developer.mozilla.org/en-US/docs/Web/CSS
cmills can you please elaborate this point a little. I am getting confused on this point. Thanks.

OK, no problem.

So all of our reference pages for CSS selectors, properties, datatypes, etc. live in the documentation hierarchy as children of the https://developer.mozilla.org/en-US/docs/Web/CSS page (assuming we are talking about the en-US locale).

This means that each one of the pages you would be creating for this work would live under there too.

So for each one you need to create a new page that is a subpage of https://developer.mozilla.org/en-US/docs/Web/CSS.

To do this, go to that page and crete the subpage by selecting the "gear" menu option "New sub-article". This will take you to the new page screen, in which you can paste in your page template and then save it.

A tip — when you first create the new article, set the correct page title (e.g. ":past"), write some placeholder content into the main content area (e.g. "content here") and then immediately save it. This means that on future page edits, your page content will be saved locally so if you lose it for some reason (e.g. your browser crashes), you can go back to the page and restore it.

This safety mechanism doesn't work if you've not actually saved the new page yet.

Comment 13

[revanthmk23200]

I would like to contribute to this project, can anyone guide me on getting started

Comment 14

[Janet Swisher]

(In reply to revanthmk23200 from comment #13)

I would like to contribute to this project, can anyone guide me on getting started

Hi! Thanks for your interest in contributing! Please read the previous comments to see what needs to be done. You need to create an account on https://developer.mozilla.org using your GitHub credentials. After you have done that, reply here with your MDN username, so someone can give you the page creation privilege.

Comment 15

[revanthmk23200]

(In reply to Janet Swisher from comment #14)

(In reply to revanthmk23200 from comment #13)

I would like to contribute to this project, can anyone guide me on getting started

Hi! Thanks for your interest in contributing! Please read the previous comments to see what needs to be done. You need to create an account on https://developer.mozilla.org using your GitHub credentials. After you have done that, reply here with your MDN username, so someone can give you the page creation privilege.

Hey,
I have created my account using GitHub.
username - revanthmk23200
thanks

Comment 16

[BMO Automation]

MDN Web Docs' bug reporting has now moved to GitHub. From now on, please file content bugs at https://github.com/mdn/sprints/issues/ and platform bugs at https://github.com/mdn/kuma/issues/.