@mattpocockuk Depends on the kind of data. Maybe a spreadsheet-like input would work best. In general, I'd probably tend to have different pages (different URLs/buttons/...) which share 95% of their components
@40PercentGerman One (stereo-)typical German saying is "Ich kann mich nicht daran erinnern, Ihnen das Du angeboten zu haben" ("I don't remember offering you "Du") if you've used "Du" and the other person is not comfortable with it
@40PercentGerman To make it even more complicated: This is changing. My doctor (I'd guess 2-3 years older) started with "Du" and it was totally fine (even though it's a rather formal relationship). Working in IT: In my bubble, everyone uses only "Du", "Sie" would be considered rather weird
@adamsilverhq Clearly yes, the more interesting question is: Should it always be visible? Probably not. Sometimes it would distract from the content (e.g. a spreadsheet-like application). The more the layout is linear (text, forms) the more likely a visible one would make sense maybe? 🤔
You asked (many times 🙃) and we heard you! Over the next year we'll be releasing new features including:
🔥 Tab grouping
🔥 Vertical tabs
🔥 Native profile management
Get ready because browsing on Firefox is about to get a whole lot better.
@adamsilverhq For the other 70% of the users - sure. I can have a product with amazing usability optimized for e.g. a PlayStation controller which might exclude screenreader, keyboard, touchscreen, mouse users etc. Might be an accessibility but not necessarily an usability issue
We just published the first beta for React 19! This beta release is for collecting feedback and preparing libraries for the next major version of React.
To see what's included, check out the release post:
https://t.co/dnGcbIRH6O
@tmcw I guess it depends on what changes you expect to happen in the future. Props are more explicit, thus easier for component-internal changes or Storybook listings. Maybe another option: Explicit prop-only component API and 1 level above, you use the Context API?
@thekitze@playwrightweb Waiting for a never matching selector should do the trick. Recording the tests (https://t.co/S4VOR80pIc) also kinda stops the page. Maybe that helps, too
@firefox My girlfriend is about to move away from Firefox due to the lack of a powerful tab management solution like e.g. Chrome has 🙈 Besides that, I often hear complaints about its performance which seems to be more of a marketing than a technical issue nowadays
📢 We're excited to share our new Firefox Developer Experience blog:
https://t.co/Jn7d0CLDwK
We’ll share our latest developments, insights, and best practices for web development, browser automation, and cross-browser testing
@kettanaito I have some struggles with the V2 route definitions. My applications requires deeply nested routes where each level has its own layout route. I constantly pick the wrong file to edit either the index page or the layout page. Every route file named route.tsx doesn't help either...