Aha, the site seems to have `<table style="display:inline-block">`. I can indeed imagine that that could produce different results, since it won't get Chrome's automagic table-boxes-behave-as-if-they-had-border-box-styling behavior. That will trivially get the box-sizing value that we provide for `<table>`, yeah, which is why we draw the purple boxes as different sizes here and Chrome draws them as the same size. I'm going to guess/hope that `<table style="display:inline-block">` is vanishingly rare on the internet, so I hope the web doesn't depend on Chrome's behavior here? So, following up on my assessment in comment 5: - I'm hoping the web *doesn't* depend on Chrome's behavior (only one webcompat issue so far [?] which seems pretty edge-casey - Chrome's behavior **does** seem pretty arcane/crazy, so it's non-obvious that we'd want to standardize on it (even if some part of the web did depend on it).
Bug 1520018 Comment 9 Edit History
Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.
Aha, the site seems to have `<table style="display:inline-block">`. I can indeed imagine that that could produce different results, since it won't get Chrome's automagic table-boxes-behave-as-if-they-had-border-box-styling behavior. That will trivially get the box-sizing value that we provide for `<table>`, yeah, which is why we draw the purple boxes as different sizes here and Chrome draws them as the same size. I'm going to guess/hope that `<table style="display:inline-block">` is vanishingly rare on the internet, so I hope the web doesn't depend on Chrome's behavior here? So, following up on my assessment in comment 5: - I'm hoping the web *doesn't* depend on Chrome's behavior (only one webcompat issue so far [?] and it seems pretty edge-casey) - Chrome's behavior **does** seem pretty arcane/crazy, so it's non-obvious that we'd want to standardize on it (even if some part of the web did depend on it).