Sabitlenmiş Tweet
Tim Kraut
1.1K posts

Tim Kraut
@Tim_Kraut
Senior Frontend Developer, working for AWESOME! Software, Mastodon: https://t.co/GV3WXv4Skq, Bluesky: https://t.co/PIkaWyS6JM
Köln, Deutschland Katılım Ocak 2012
425 Takip Edilen120 Takipçiler

@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
English

@AlemTuzlak Oh no, this sucks! Maybe you have luck and can recover it using git reflog?
English
Tim Kraut retweetledi

@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
English

@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
English

@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? 🤔
English
Tim Kraut retweetledi
Tim Kraut retweetledi

JS-free dynamic popups, nice performance boost, sourcemap management and bug fixes, read what’s new in @FirefoxDevTools 125:
fxdx.dev/firefox-devtoo…
English

@adamsilverhq Maybe entering a 6-digit second factor code? Not sure about it though
English

@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
English

@Tim_Kraut Do you think you can have good usability if say 30% of users cannot use it?
English
Tim Kraut retweetledi

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:
react.dev/blog/2024/04/2…
English

@thekitze @playwrightweb Waiting for a never matching selector should do the trick. Recording the tests (#recording-a-test" target="_blank" rel="nofollow noopener">playwright.dev/docs/codegen#r…) also kinda stops the page. Maybe that helps, too
English

any idea how to get @playwrightweb *not* to close the chromium browser so I have time to copy and enter the 2FA code that adobe sends to my email?
I'm trying with page.pause, page.waitForTimeOut, new Promise, etc. but the browser still closes no matter what

English

@LeaVerou @vuejs Haven't build a modal yet (only a tooltip component) with this library but floating-ui.com might be worth a look
English

Folks using @vuejs 3: what do you use for modal dialogs, and how much do you like it?
Somerville, MA 🇺🇸 English
Tim Kraut retweetledi

📢 We're excited to share our new Firefox Developer Experience blog:
fxdx.dev
We’ll share our latest developments, insights, and best practices for web development, browser automation, and cross-browser testing
English

@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...
English

📰 Today, I write about my struggle with Remix.
redd.one/blog/my-strugg…
#javascript #remix #frontend
English
Tim Kraut retweetledi

Didja know Lighthouse has a diff tool? 🤔 Compare two reports and see all the changes.
googlechrome.github.io/lighthouse-ci/…




English






