Closed
Bug 1170318
Opened 11 years ago
Closed 11 years ago
Reach out to add-on authors to get them to remove now-invalid CSS "box-sizing: padding-box" (migrating to "border-box" or "content-box" as-needed)
Categories
(WebExtensions :: General, defect)
WebExtensions
General
Tracking
(Not tracked)
RESOLVED
INVALID
People
(Reporter: dholbert, Unassigned)
References
()
Details
(Keywords: addon-compat)
The CSSWG resolved to remove "box-sizing: padding-box", so we're removing support for it as well, as discussed in bug 1166728.
Filing this bug to track evangelism for fixing up addons code that uses "box-sizing:padding-box.
(Authors should instead use "content-box" or "border-box", depending on whether or not they want sizes to include border/padding. They have to include both border+padding, or neither. In most cases, "border-box" is probably appropriate, since content-box is the default.)
bz posted this addons MXR search query to help with discovering addons that need fixing:
https://mxr.mozilla.org/addons/search?string=box-sizing%3A+padding-box&find=&findi=&filter=^[^\0]*%24&hitlimit=&tree=addons
| Reporter | ||
Updated•11 years ago
|
Summary: Remove "box-sizing: padding-box" from addons → Reach out to add-on authors to get them to remove now-invalid CSS "box-sizing: padding-box"
| Reporter | ||
Updated•11 years ago
|
Summary: Reach out to add-on authors to get them to remove now-invalid CSS "box-sizing: padding-box" → Reach out to add-on authors to get them to remove now-invalid CSS "box-sizing: padding-box" (migrating to "border-box" or "content-box" as-needed)
Updated•11 years ago
|
Keywords: addon-compat
Comment 1•11 years ago
|
||
Using the addon-compat keyword in the original bug and setting the right milestone when it lands is sufficient. We do outreach for every release and don't track it through Bugzilla.
Thanks for the heads-up!
Status: NEW → RESOLVED
Closed: 11 years ago
Resolution: --- → INVALID
| Assignee | ||
Updated•7 years ago
|
Component: Add-ons → General
Product: Tech Evangelism → WebExtensions
You need to log in
before you can comment on or make changes to this bug.
Description
•