I was just about to create a bug on the chromium issue tracker, but then I thought I would give it a try here first.
Try having a look at this site:
http://www.norabrowndesign.com/css-experiments/border-image-frame.html
However it appears that chrome does support border-image-outset now or so I thought.
It responds to the command, but does not behave as I would expect.
Is moves the images outward and thus creates more whitespace around the content instead of less.
Reading the spec I am not sure if chrome is wrong in doing what it does, but it certainly seems the author of the linked site expected something else.
Further more, if the present behavior is correct then I cannot see what the purpose of it is. And the problem with the large border image, will have no solution at all.
So what is it, should I submit a bug or?
I believe Chrome behaves as it should.
border-image-outsetis supposed to extend the border image area beyond the border box. It seems to do that in Chrome.Removing the whitespace around the content would require the opposite which can be achieved with the help of
border-image-width.border-image-widthdivides the border image area and is basically the counterpart toborder-image-slice(which divides the border image). It’s initial value is1(multiples of the corresponding computedborder-width). So without assigning aborder-image-widthevery slice would be resized toborder-width.See border-image-width at w3.org
To remove the whitespace around the content while keeping the size of the border image you would have to reduce
border-widthand setborder-image-widthto an appropriate value.Try the following changes in the example from your question: