Get rid of .htmlelt in en-US pages

RESOLVED FIXED

Status

Developer Documentation
HTML
--
enhancement
RESOLVED FIXED
2 years ago
2 years ago

People

(Reporter: teoli, Assigned: sebo)

Tracking

(Depends on: 1 bug, Blocks: 1 bug)

Details

(Reporter)

Description

2 years ago
We are replacing .htmlelt by .properties and a table format (see bug 1207344#c6).

Current state for .htmlelt :
.htmlelt: 111
[ https://developer.mozilla.org/en-US/search?css_classnames=htmlelt ]
(Assignee)

Updated

2 years ago
Assignee: nobody → sebastianzartner
(Assignee)

Comment 1

2 years ago
What macros do you refer to? Shouldn't we split that work up into a separate issue?

Sebastian
Flags: needinfo?(jypenator)
(Assignee)

Comment 2

2 years ago
(In reply to Sebastian Zartner [:sebo] from comment #1)
> Shouldn't we split that work up into a separate issue?

I mean track removing those macros in a separate bug report and concentrate on replacing the .htmlelt lists by .properties tables in this one.

Sebastian
(Reporter)

Comment 3

2 years ago
When I created the bug I though there will be a macro, but I was mistaken. Yes updating the list to tables is what needs to be done.
Flags: needinfo?(jypenator)
Summary: Get rid of .htmlelt in pages and macros → Get rid of .htmlelt in pages
(Assignee)

Comment 4

2 years ago
At some point we may store the related data in a DB and create a macro similar to 'cssinfo'. That would probably let us get rid of (at least) the 'no_tag_omission' macro.
If that's wanted, I suggest you file bugs for creating the HTML DB and creating the macro, so we don't forget about it.

Sebastian
(Reporter)

Comment 5

2 years ago
I've made tests there and it happens that except for specific cases, most texts in this table are different from one element to the other (a few exception), so I think storing all this in a HTML DB is overkill; especially as this info is used at one single place.
(Assignee)

Comment 6

2 years ago
(In reply to Jean-Yves Perrier [:teoli] from comment #5)
> I've made tests there and it happens that except for specific cases, most
> texts in this table are different from one element to the other (a few
> exception), so I think storing all this in a HTML DB is overkill; especially
> as this info is used at one single place.

Fine for me.

I've finished replacing the .htmlelt lists by .properties tables on all English pages now.

Same question as in bug 1212767 comment 9:
Doing this for pages in other locales is the responsibility of the localization teams, right?

Sebastian
Flags: needinfo?(jypenator)
(Reporter)

Comment 7

2 years ago
Yes, we should open a bug for fr, de, ja (we need to double check). And a bug for the remaining locales (we don't have regular contributors).

Marking these bugs as blocking 1207344 and morphing this one in en-US.

That way we can track progress in more details [keeping the pleasure to close bugs to mark progress], engage volunteers in specific locales and know when we can tell Stephanie to remove .htmlelt from the CSS (which is the technical goal of the project, the doc goal being having unified tables).
Flags: needinfo?(jypenator)
(Reporter)

Updated

2 years ago
Summary: Get rid of .htmlelt in pages → Get rid of .htmlelt in en-US pages
(Assignee)

Comment 8

2 years ago
Good, so I can close this bug then.

Sebastian
Status: NEW → RESOLVED
Last Resolved: 2 years ago
Resolution: --- → FIXED
(Assignee)

Updated

2 years ago
Depends on: 1220137
You need to log in before you can comment on or make changes to this bug.