- From: Lea Verou <lea@verou.me>
- Date: Tue, 23 Feb 2016 04:45:39 -0500
- To: Craig Francis <craig.francis@gmail.com>
- Cc: Ojan Vafai <ojan@chromium.org>, Xidorn Quan <quanxunzhen@gmail.com>, Simon Fraser <smfr@me.com>, "Tab Atkins Jr." <jackalmage@gmail.com>, www-style list <www-style@w3.org>, Aleks Totic <atotic@google.com>, Elliott Sprehn <esprehn@google.com>, Ian Kilpatrick <ikilpatrick@google.com>
> On 23Feb, 2016, at 04:37, Craig Francis <craig.francis@gmail.com> wrote: > > Just to add to this (again, going a bit off topic, please feel free to ignore).... > > [snip] > > And I personally don't see myself using ResizeObserver, as it will take a very long time for it to be implemented, and I can't see how it will make any improvements over my current JavaScript "solution", which at least supports legacy browsers. > > Craig Again, completely agreed with Craig. I’m not quite sure how this convoluted ResizeObserver solution is better than what we currently have, given that it's also same origin (or did I misunderstand?). Good thinking re:general APIs first and shortcuts later, but there *is* such a thing as too much generalization. Let's not turn the Web platform into Java, please. Also not sure what is meant by `// inside the frame` in the code sample. Is this code supposed to be called from inside the iframe? In that case, it doesn't solve the overwhelming majority of use cases for this, where the parent wants to resize the iframe and the iframe has no idea. ~Lea
Received on Tuesday, 23 February 2016 09:46:02 UTC