-
Notifications
You must be signed in to change notification settings - Fork 672
Bug 1492018: Use .blockIndicator for styling {{SeeCompatTable}}
#4962
Conversation
jwhitlock
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks @ExE-Boss.
Kuma changes require a Bugzilla ticket. I think we can reuse https://bugzilla.mozilla.org/show_bug.cgi?id=1486527, seems related to snugging.
I searched for a page where this would make a difference. https://developer.mozilla.org/en-US/docs/Web/CSS/offset-distance looked like a good candidate. However, it looks snugged already in Safari, and the change in PR #4961 will fix it for Chrome and Firefox (to be deployed today). Do you know of a page where this change will make a difference?
|
This isn’t necessary for indicator snugging. It’s necessary to be able to remove the See mdn/kumascript#788 for details. |
|
There's no mention of |
|
I meant specifically commit mdn/kumascript@d0c3a47. Once this is merged, I can make a follow-up to mdn/kumascript#788, where I’d remove the |
.experimental.overheadIndicator for styling {{SeeCompatTable}}.experimental.blockIndicator for styling {{SeeCompatTable}}
83d5dd0 to
0445685
Compare
.experimental.blockIndicator for styling {{SeeCompatTable}}.blockIndicator for styling {{SeeCompatTable}}
|
review?(@jwhitlock): I’d say this is ready for review. |
|
I think I'm the wrong person to review this. I can review style changes if you are trying to fix something that I can see on a particular page on MDN, because I can load the page in my browser before and after the change and see what the effect is. I'm not aware of any pages that this change would make a visual difference on. This appears to be a refactoring of classes for some quality goal in the CSS source, which isn't clear to me. I think @schalkneethling or @hobinjk are better suited to review. |
This is necessary for mdn/kumascript#830 (diff). Without this, if mdn/kumascript#830 is merged to production as is, any usage of the |
|
@schalkneethling or @hobinjk, please take a look when you have a chance. There's several PRs in the same topic, and I've documented my understanding of the issue. I'd also support closing this and related PRs, it is hard for me to justify spending more time on what appears to be low-priority cleanup work. |
|
As mentioned, it would be super useful if you could merge the work here into #4979 |
|
I have now locally developed a better solution than this. |
…4979) See [bug 1492018](https://bugzil.la/1492018) for details. ## TODO - [x] Add the `.properties` class to the `:matches(…)` selector (see [`ime-mode`](https://developer.mozilla.org/docs/Web/CSS/ime-mode) for a case where this is necessary) - [x] Push remaining commits (3/3) ## Changes: - Add support for snugging `.blockIndicator`. - Add indicator colour override classes (obsoletes #4962): - `.indicator-info` - grey - `.indicator-version` - blue - `.indicator-warning` - yellow - `.indicator-danger` - red - Use classes instead of `style` attributes for ES7/Harmony and JSOverrides. - Fix `<pre>` block and `.properties` table snugging. --- review?(@schalkneethling)
This is a follow‑up to mdn/kumascript#788, which added the standard
.overheadIndicatorclass to the{{SeeCompatTable}}macro.Depends on #4979