Closed
Bug 564699
Opened 15 years ago
Closed 13 years ago
request for "border-image-outset" in -moz-border-image shorthand
Categories
(Core :: CSS Parsing and Computation, enhancement)
Core
CSS Parsing and Computation
Tracking
()
RESOLVED
DUPLICATE
of bug 497995
People
(Reporter: giorgio.liscio, Unassigned)
References
()
Details
(Keywords: css3)
Attachments
(1 file)
(deleted),
text/html
|
Details |
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.2; WOW64; en-US; rv:1.9.3a5pre) Gecko/20100508 Minefield/3.7a5pre ( .NET CLR 3.5.30729)
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.2; WOW64; en-US; rv:1.9.3a5pre) Gecko/20100508 Minefield/3.7a5pre ( .NET CLR 3.5.30729)
hi,
http://www.w3.org/TR/css3-background/#the-border-image
http://www.w3.org/TR/css3-background/#border-image-outset
http://www.w3.org/TR/css3-background/border-image.png
Reproducible: Always
Comment 1•15 years ago
|
||
Looks like this was added after we implemented -moz-border-image....
Status: UNCONFIRMED → NEW
Ever confirmed: true
the border-image-outset property works like a "negative padding"
this is useful when the borderimage acts as a "background" too
about what i just said, negative paddings can be a good solution too, instead of add a new random property to css
padding:-120px;
instead of:
border-image-outset:120px;
news here? will be this fixed in gecko 2 first release?
thank you
Comment 5•14 years ago
|
||
If there were, you'd have seen it here.
This is a good bit of work since it breaks a whole bunch of assumptions about where a border is and isn't drawn.
Comment 6•13 years ago
|
||
Any news on this? It is now implemented in Chromium, and the corresponding specification is in CR.
Comment 7•13 years ago
|
||
This was fixed a few weeks ago
Status: NEW → RESOLVED
Closed: 13 years ago
Resolution: --- → DUPLICATE
You need to log in
before you can comment on or make changes to this bug.
Description
•