I'd love to make sure this CSS visibility filtering worked well for screenreaders and other accessibility tools but that ticket was pushed down the backlog in favor of replacing native inputs with custom inputs that better match our branding guidelines. I'd love to slap an input box above a table and call it done but the product owners and designers that fill my backlog have other ideas. Not sure what this means? Why can't you batch-render on the web?įiltering a list is easy when all the data exists on the client and has no advanced filtering controls. Recalc of dims, either eager or lazy, will be necessary for any drawing system (you're just looking at whether the request for a component size is an internal implementation detail or an application API). Firefox it's on a "frame" basis (an internal frame object, not HTML element). For Chrome, this is unfortunately a global flush, but for e.g. It's true if the layout has changed since last size read, as layout changes will trigger a layout flush, requiring recalc (which are done lazily). > asking for element sizes causes the browser to recalculate the layout There is no major fundamental difference between web and non-web in this regard: it's just rendering content to a screen. They are often not performant in non-web environments. They are often very performant on the web (creating your own virtual list implementation is straightforward). I'm not refuting that they exist, I'm just refuting absolutist statements about their generalised perfection. I've used virtual lists (outside the web). Nah, it can be done but Google and Mozilla are focusing on JS and failling to implement even the most basic customization stuff for native components, they are probably not even aware that things can be done better because their heads are to deep into the web ass and not seen any good Desktop or mobile toolkit in their lives. IMO you don't have experienced with this powerfull tookits, your imagination is lacking and you think that shit that existed for so many years is impossible to do. You get a basic component for simple use cases and a very advanced one if you need stuff like resizable columns, re-ordering columns, sort-able columns. It is super efficient and was solved in many toolkits, I am sure it is done in Flex4.Īn example from Flex4 is the DataGrid and AdvancedDataGrid. This was solved, you render the visible items, and a few extra items before and after, then when the user scrolls you never render new items widgets but recycle the existing ones and refresh their state to match. With current web tech we spend to much time on re-creating functionality(not styling), have often you see borken menus or dropdowns on websites? Wouldn't a native dropdown that could be styles or a native menu widget that could be styles would make things much better ? TLDR, web needs widgets like desktop toolkits for people that want to focus on bussiness logic, for the rest they can use more simple things they create themselves or npm install or buy some more cool widgets. I did not say it is impossible, but it is not a simpel thing like on a toolkit where you wouldģ setup special rendering functions for some columns (only if needed)Īnd that is all, you get performance, sorting, column resizing, re-ordering for free, you can focus on the business logic and not on creating a DataGrid widget from scratch and fixing bugs for years until you get to 20% of the performance and features of similar desktop native one.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |