Lift integer restriction on border-image-width and border-image-outset

• Component: CSS
• Status: RESOLVED CONFIGURATION CHANGED

[Ryosuke Niwa]

Consider merging https://chromium.googlesource.com/chromium/blink/+/69945681720a72bd94a1cb34b3e30d1851aa08a0

border-image-{width,outset} should accept percentages, lengths,
numbers, and auto. A number represents a multiple of the computed
border-width, and should not be restricted to integral values.

[Ahmad Saleem]

Test Case - border-image-width-numbers-computed-style.html - https://jsfiddle.net/oxwa2m0d/show

*** Safari 15.6.1 on macOS 12.5.1 ***

FAIL elm.borderImageWidth should be 0 5.5 4.4 3.3. Was 0 5.5 4.400000095367432 3.299999952316284.
FAIL elm.borderImageOutset should be 2.5 0 1.4 1.9. Was 2.5 0 1.399999976158142 1.899999976158142.
PASS successfullyParsed is true

*** Safari Technology Preview 151 ***

PASS elm.borderImageWidth is "0 5.5 4.4 3.3"
PASS elm.borderImageOutset is "2.5 0 1.4 1.9"
PASS successfullyParsed is true

*** Chrome Canary 106 ***

PASS elm.borderImageWidth is "0 5.5 4.4 3.3"
PASS elm.borderImageOutset is "2.5 0 1.4 1.9"
PASS successfullyParsed is true

*** Firefox Nightly 105 ***

PASS elm.borderImageWidth is "0 5.5 4.4 3.3"
PASS elm.borderImageOutset is "2.5 0 1.4 1.9"
PASS successfullyParsed is true

________________

Test Case - border-image-width-numbers.html - https://jsfiddle.net/g4c019x5/show

*** Safari 15.6.1 on macOS 12.5.1 ***

Red splashes then "Green" box

*** Safari Technology Preview 151 ***

Red splashes then "Green" box

*** Chrome Canary 106 ***

Red splashes then "Green" box

*** Firefox Nightly 105 ***

Green box

______________

I think at least in STP 151 both issues are fixed now. Should we keep it open or this can be considered fix? Thanks!

[Alexey Proskuryakov]

Drawing red before the subresource png loads wouldn't be part of this issue, so marking resolved.