@scottjehl@mstdn.social
@scottjehl@mstdn.social avatar

scottjehl

@scottjehl@mstdn.social

Independent Web Designer/Dev. Accessibility & Performance Fan. Author, Speaker, Mediocre surfer. Working on a Web Components course!

Alum: WebPageTest, Filament Group, jQuery

This profile is from a federated server and may be incomplete. Browse more on the original instance.

zachleat, to random
@zachleat@zachleat.com avatar

they’re gathering.

scottjehl,
@scottjehl@mstdn.social avatar

@zachleat Amazing. Hope it goes great!

scottjehl, to random
@scottjehl@mstdn.social avatar

Just flipped this Kickstarter pre-launch page on for a project I want to produce this spring. I'm planning to start the campaign very soon in case you'd like to be kept in the loop 🥳 Thank you! https://www.kickstarter.com/projects/scott-jehl/web-components-demystified

scottjehl, to random
@scottjehl@mstdn.social avatar

I’m sure you’ve all heard already but I wanted to comment on it myself. It’s true that after at 10 or so seasons of attempts, our shuffleboard team secured a spot in the playoffs last night. I’ll take a few questions

scottjehl, to random
@scottjehl@mstdn.social avatar

recording for my upcoming web components online course has reminded me of the challenges of recording audio. During the day, there's construction buzz sawing in the background. At night, kids are home or trying to sleep. And now that I'm in NYC, there are also

HORNS

scottjehl, to random
@scottjehl@mstdn.social avatar

Anyone used Descript here? Some of the features seem like pretty major time savers for video work, particularly remembering how much time I've spent manually removing and overdubbing phrases in the past. Of course, the best features will mean training a model on my own voice, which seems like the sort of thing I might regret one day, even if the data privacy appears to be well-considered.

scottjehl, to random
@scottjehl@mstdn.social avatar
scottjehl,
@scottjehl@mstdn.social avatar

@cferdinandi hey thanks! We rented 25ft RVs from Cruise America in SLC to do the round trip. Drove to the Zion/Bryce area for the first two nights, and arches area for the next two. One park per day. Bryce was our fav. Maybe the most surprising part was how much open area there is to just camp in BLM land. We booked ahead not knowing how it’d go, and because we had 4 RVs with young kids, but next time I’d be more spontaneous. That said, Gold Bar campground in Moab was incredible.

scottjehl, to random
@scottjehl@mstdn.social avatar

Handmade landing pages remain the most fun part of doing websites for me

scottjehl, to random
@scottjehl@mstdn.social avatar

Friday at 8PM is a great time to soft-launch a thing right? 🥳

This something I intend to make! I'm excited. It'll mainly be about Web Components, but in the context of building resilient, fast, accessible websites. A holistic take!

I'm planning a different approach for it, using a presale (soon) to gauge interest and shape the scope of what I end up making. I'll appreciate some help making noise about it soon, but for now it's a coming soon page and email collector :)

https://scottjehl.com/learn/webcomponentsdemystified/

scottjehl, to random
@scottjehl@mstdn.social avatar

Think I've found a good place to use @simplebits Vault Alarm font 😎

scottjehl, to random
@scottjehl@mstdn.social avatar

Papyrus 2 was really good

scottjehl, to random
@scottjehl@mstdn.social avatar

How would you build Wordle with just HTML & CSS?

In this blog post, I talk about why I think that'd be a good interview question, and I take a stab at answering it as well.

https://scottjehl.com/posts/wordleish/

scottjehl,
@scottjehl@mstdn.social avatar

Also, I'd love to know if anyone can figure out the three states without adding JS. I have ideas but I haven't tried them yet. I bet somebody like @argyleink could do it... :)

scottjehl, to random
@scottjehl@mstdn.social avatar

I was tinkering a bit today and it turns out you can pull off a decent amount of Wordle's gameplay with just HTML and CSS. Fun little form validation and CSS selector refresher experiment, anyway.

https://codepen.io/scottjehl/details/LYvQxqa

scottjehl,
@scottjehl@mstdn.social avatar

There's another linked fork in there that adds a few lines of JS to validate the exact letter matches so that the pattern attribute can drive the tan colors. It made me wish HTML and CSS validation had a little finer grain, ...or that the pattern attribute accepted and exposed capturing parentheses to selectors? :)

scottjehl,
@scottjehl@mstdn.social avatar

...really wanted to find a way to get that second demo's behavior without JS but I didn't get there. I even tried making the qwerty keyboard out of loads on radio inputs at one point.

...don't try that.

scottjehl,
@scottjehl@mstdn.social avatar

As an aside, I'd love to see frontend engineer interviewers ask folks how they'd do things like this. "How would you build [popular app] if you could only use HTML and CSS? Which features would require you to use JS to pull off even in a basic way? Can you envision a fictional future standard that would make this easier?"

It would reveal a lot about a candidate's knowledge of web standards, and ideally select for folks who can help us all move away from JS over-reliance!

elly, to random
@elly@front-end.social avatar

Front-end development’s identity crisis
🔗 https://ellyloel.com/blog/front-end-development-s-identity-crisis/

scottjehl,
@scottjehl@mstdn.social avatar

@elly Great post. I've stuck with "web designer & developer" for a while and can certainly relate.

scottjehl, to random
@scottjehl@mstdn.social avatar

Lost-cause decisions in standards and browsers can be reversed when the community makes a strong, persistent case. I've seen it happen first-hand with responsive <video>, and responsive images before that.

One decision I want to see reversed is Webkit's lack of IS attribute support, which lets us write Web Components that customize built-in HTML elements. IS is a standard. Works in Chromium & Firefox. It's a great pattern for applying enhancements, especially in forms.

https://github.com/WebKit/standards-positions/issues/97

scottjehl,
@scottjehl@mstdn.social avatar

@tbroyer those are great too, but I am not sure I agree that they solve the same use cases. Either way, this is an argument in favor of a standard that is already supported in a couple browsers and favored heavily by developers already too. I find that it’s pretty common for developers to reach for custom builtins and only later realize that they don’t work in Safari.

scottjehl,
@scottjehl@mstdn.social avatar

@tbroyer hmm. I mean, it’s the same situation as any standard that one browser doesn’t support, in that you can look it up and find out. But there’s a reasonable path when learning web components to land on extending an existing element instead of creating a new one or wrapping it… especially for small enhancements to form elements or elements that can’t be wrapped, like a list item or something.

scottjehl,
@scottjehl@mstdn.social avatar

@tbroyer Sorry, weekend reply delay. :) I'm interested in understanding what you mean here. Are you describing extending a built-in (HTMLButtonElement) to define a custom element (my-button)? I wasn't aware that the spec or browsers offer that option, but I'm probably just not understanding what you mean. Either way, I am not sure I follow why a standard should be labeled experimental just because it has yet to gain Safari support. Are there reasons I'm forgetting?

scottjehl,
@scottjehl@mstdn.social avatar

@tbroyer Would you happen to have a link to the proposal (spec?) you're referencing? I'm not sure I understand how custom attributes relate to or replace the WC lifecycle for customizing a built-in element. This is the first time I've heard the two discussed as redundant, and that's probably on me. Thanks!

scottjehl, to random
@scottjehl@mstdn.social avatar

Happy INP Is A Core Web Vital Day to all who are not rendering their HTML through a rabbit warren of modern javascript!

scottjehl, to random
@scottjehl@mstdn.social avatar

So, I mentioned that I plan to produce a new premium online course this spring. It's going to be about Web Components, and it's going to aim to cover them comprehensively, both in fine detail and in the wider context of how we can use them in our work with various tooling approaches and environments, all with a goal of building faster, more accessible, and more resilient websites.

A LOT has changed with Web Components recently, even in just the last year. The time feels right. Stay tuned!

  • All
  • Subscribed
  • Moderated
  • Favorites
  • anitta
  • kavyap
  • everett
  • thenastyranch
  • magazineikmin
  • ngwrru68w68
  • DreamBathrooms
  • modclub
  • Youngstown
  • slotface
  • PowerRangers
  • osvaldo12
  • InstantRegret
  • rosin
  • Leos
  • hgfsjryuu7
  • Durango
  • vwfavf
  • khanakhh
  • tester
  • GTA5RPClips
  • ethstaker
  • mdbf
  • cubers
  • tacticalgear
  • normalnudes
  • cisconetworking
  • provamag3
  • All magazines