12:06
<peperonin>

Hello! I came here to ask about

HTML 5 spec by WHATWG, 8.6 Timers says:

If nesting level is greater than 5, and timeout is less than 4, then set timeout to 4.

I have to ask, why is exactly 5 and why we even have to increase timeout to a value, that is bigger than 4 or just 4 itself?

P.S. - I know about motivation of certain hosts like Chromium, but I am curious about the reasons of having such restrictions in HTML5 Spec.

12:43
<Ms2ger>
To achieve interoperability between those browsers
12:44
<peperonin>
@ms2ger:igalia.com Could you provide more details, please?
12:45
<Ms2ger>
I'm not sure what else you're asking? The point of a web standard is to make sure different browsers handle the same code in the same way
13:00
<peperonin>
I'm not sure what else you're asking? The point of a web standard is to make sure different browsers handle the same code in the same way
I am asking about certain restrictions of implementation of HTML5 Spec. Spec says "If nesting level is greater than 5, and timeout is less than 4, then set timeout to 4." and I want to know why is exactly 5 and why we even have to increase timeout to a value, that is bigger than 4 or just 4 itself?
13:03
<Ms2ger>
You're saying you understand why browsers do that, right?
13:05
<peperonin>
You're saying you understand why browsers do that, right?
Yes. Why?
13:06
<Ms2ger>
If browsers do it, it should be in the standard. Otherwise the standard is just extremely boring science fiction
13:08
<peperonin>
So browsers are writing the HTML 5 Spec and not WHATWG?
13:09
<Ms2ger>
What do you think WHATWG is?
13:31
<Domenic>
Hixie wrote about this recently, by coincidence. http://ln.hixie.ch/?start=1721260117&count=1
16:28
<peperonin>
Hixie wrote about this recently, by coincidence. http://ln.hixie.ch/?start=1721260117&count=1
Ty