- From: Andy Earnshaw <notifications@github.com>
- Date: Thu, 28 Feb 2019 02:29:01 -0800
- To: w3c/webcomponents <webcomponents@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
Received on Thursday, 28 February 2019 10:29:22 UTC
> I'm happy to discuss with my colleagues And I appreciate that, thank you. > I think your confirmation bias in favor of making everyone implement a new API is too strong here. I feel that you're being somewhat disrespectful here. Yes, I proposed a new API, because virtual scrolling is used widely on the web and I feel that making it a first-class feature is a good idea, but all I really wanted was to start a discussion around it and see if others also felt it was a good idea. Maybe it *is* confirmation bias—I too think it un-coincidental that all browser vendors independently arrive at element size limits—, but it's nothing to do with "making everyone implement a new API", all I'm looking for is a way forward. It's true, I would much prefer one that doesn't involve kicking the can down the road, which I feel increasing maximum sizes is. Maybe this issue is too obscure for you to take the time to discuss why you feel it doesn't require a new API but, in any case, a bit of professional courtesy would be nice. -- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/w3c/webcomponents/issues/791#issuecomment-468220911
Received on Thursday, 28 February 2019 10:29:22 UTC