121–130 of 223 posts
Earlier quoted context omitted.
That seems like a bizarre reason not to use it, given that it's strictly a performance optimisation, and browsers will simply ignore CSS rules they don't understand.
I imagine that it could cause accusations from Apple that Google is trying to take their customers out of the ecosystem, putting a nice cash flow at risk.
Google Search Console is just unusable for browsing large data sets due to this issue.
Earlier quoted context omitted.
What you need is Open UI. The browser vendors are working on it. https://open-ui.org/ > The purpose of Open UI to the web platform is to allow web developers to style and extend built-in web UI controls, such as dropdowns, checkboxes, radio buttons, and date/color pickers. > To do that, we'll need to fully specify the component parts, states, and behaviors of the built-in controls, as well as necessary accessibility…
https://open-ui.org/charter > Most recent revision: April 1, 2020 That doesn't inspire confidence...
Earlier quoted context omitted.
Microsoft is building a web component framework: https://developer.microsoft.com/en-us/fluentui#/get-started/...
I went to check this out, seems they're only focusing on React and beyond that, a maintainer mentions they're looking for funding. Doesn't sound too promising... https://github.com/OfficeDev/office-ui-fabric-core/issues/12...
Earlier quoted context omitted.
You should see what you can do with and these days, no more do your native browser elements have to look like complete dog to receive free native device controls
I can't believe these elements slipped under my radar for so long - I have a site with no Javascript (outside of Google Analytics anyway) and and have helped me keep it that way.
Earlier quoted context omitted.
Browser support aside, it seems very counterintuitive. https://developer.mozilla.org/en-US/docs/Web/CSS/contain suggests that it can cause pages to render differently, which is very strange, considering that the description implies that it only effects when the browser repaints/re-processes region, and not what the result is.
Browsers give no control over when areas are repainted. If you change a bit of CSS or DOM, it will be repainted in the next frame. There is no way to say 'dont paint this yet'. The thing the contain property does is ensure that a particular Dom change won't affect pixels outside the element involved, which means the browser won't need to do any extra repainting.
https://developer.mozilla.org/en-US/docs/Web/CSS/content-vis...
Earlier quoted context omitted.
I think it’s a funding issue. A lot of desktop GUI toolkits were funded by the people who created the platform themselves so they had every incentive to make it both flexible and consistent. When I look for a web component, the few component libraries that cover several different components are often extremely incomplete. Often they’re just side projects of a company or even an individual. No one is putting in the mo…
I think that's part of it. I also think that, as far as interactive components, virtually nothing on the web has had a shelf life of longer than 3-5 years. Ever. The lone exception are the base HTML components. I think the last actual change to those was making textarea resizable, and that's kind of a browser override to the spec as much as anything else. Essentially nothing has actually changed in form and UI elemen…
Earlier quoted context omitted.
> Modern web interfaces can be designed to be user friendly, performant, and good looking. Right. Name three examples that are all this, and still considered "good UX" by webdev standards. > Try marketing a web app Herein lies the real issue. And it predates the web. I recall a piece of documentation of Windows around 3.11 era, where the developers already threw their hands up in the air over realizing that, no matte…
I like https://airtable.com/ , https://linear.app/ , and https://height.app/ . They are all pushing the limits of interactive web apps, not always entirely successfully, but the overall product experience is mostly smooth and polished. I wouldn't really be able to say what it means to be "considered good UX by webdev standards," but I develop for the web and I like these three.
Earlier quoted context omitted.
What you need is Open UI. The browser vendors are working on it. https://open-ui.org/ > The purpose of Open UI to the web platform is to allow web developers to style and extend built-in web UI controls, such as dropdowns, checkboxes, radio buttons, and date/color pickers. > To do that, we'll need to fully specify the component parts, states, and behaviors of the built-in controls, as well as necessary accessibility…
https://open-ui.org/charter > Most recent revision: April 1, 2020 That doesn't inspire confidence...