On Thu, May 4, 2023 at 6:40 AM Andreas Haas <ah...@google.com> wrote:
> Hi Yoav, PhistucK, > > [...] > > My problem now is that with the higher limit we still violate the spec, an > with the spec test I introduced during this discussion the spec violation > is even more visible. As someone wrote before, a solution to this problem > could be to change the spec, but the same as there is no reason to keep or > remove the limit in Chrome, there is no reason to introduce such a limit > into the spec. > > Multiple experts in web performance have given reasons to keep the limit in this thread. That would be the reason to introduce it to the spec. - E -- You received this message because you are subscribed to the Google Groups "blink-dev" group. To unsubscribe from this group and stop receiving emails from it, send an email to blink-dev+unsubscr...@chromium.org. To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CAPKeNH%3DnkK6o8mZUHazY-QU6jH8O4Yw9UNqt8sb%2B8PCLaCfU%2Bg%40mail.gmail.com.
