Jake's survey is closed.

Maybe it's not the fastness that lowers the conversion rate, but something else, like maybe the fastest websites are more likely to have not-so-great design?

Accept cookies! Subscribe to our newsletter for 15% off! Hey, do you want to take a survey of how much you like our website?

i
a
i
n
'
t
r
e
a
d
i
n
g
a
l
l
t
h
a
t
i
m
h
a
p
p
y
f
o
r
y
o
u
t
h
o
o
r
s
o
r
r
y
t
h
a
t
h
a
p
p
e
n
e
d

Not saying you should but it should work

Or <script xmlns="http://www.w3.org/1999/xhtml" src="..."/>! If there's at least one element in a known namespace, browsers switch away from the XML tree view.

Right, though ARIA attributes are superglobal.

Needs bugs.webkit.org/show_bug.cgi...

In your demo, the relevant element is a flex item, which is not inline.

Here's a demo showing that actual inline doesn't work: software.hixie.ch/utilities/js...

The part about display: inline is wrong.

This:

> establishes an inline formatting context and thus contains only inline-level boxes.

Refers to what the element contains. A block box establishes an inline formatting context when it has no block-level children. The element itself is still a block.

Sure. People used to call it XHTML. :) If there's an element in a known namespace browsers will apply the UA stylesheet. If you add a script element it will run (if scripting is enabled).

I don't know if feed readers will get confused though.

It seems to me you should be able to use

<script xmlns="http://www.w3.org/1999/xhtml" src="polyfill.js"/>

Let's apply the same logic to rendering images, video and audio...

Yes. Remove it, Bruce! I know you can do it!

I've never used LinkedIn

No ragrets