@jensimmons.bsky.social
Apple Evangelist on the Web Developer Experience team for Safari & Webkit. #PwME
@jensimmons.bsky.socialI’ve thought for years the answer should be no styling! Be like a `section` or `div`. Let the developer turn it to anything. Thoughts?
@jensimmons.bsky.socialIf you write: `fieldset { appearance: base }`, what do you want the styling to be in the future??
@jensimmons.bsky.socialWhat do you want the new default styling to be for HTML fieldset? Here’s what it’s been forever — a box around things, with the legend text placed over the middle of the line at the top left. (See developer.mozilla.org/en-US/docs/W... for more.)
@jensimmons.bsky.socialThe UA style for <popover> uses currentColor for the border, which means it uses your text color. If you’ve provided no `color`, then it’s using system colors — which totally support light & dark mode. Which is exactly how `appearance: auto` will work for form controls.
@jensimmons.bsky.socialDo folks around you believe a toggle is required as part of dark mode? Why?
@jensimmons.bsky.socialWhat benefit would that have? Light-dark maps to the system setting. And color scheme tells the browser to change the system colors… are you assuming sites need toggles?
@jensimmons.bsky.socialDo you feel like adding a light/dark mode toggle to a website is necessary? Or just something you think is cool for the projects you make?
@nicolesullivan.bsky.socialReposted by @jensimmons.bsky.socialHow do you do CI for mobile? Does it work well? I’m curious about the state of the art these days.
@jensimmons.bsky.socialDark mode. Do the websites & web apps made by your team support dark mode? If not, why not?
What do you want to know most to help empower your team to support it?! What’s the blocker?
What is confusing or hard about dark mode?
@jensimmons.bsky.socialDid I bust you? 🥺
@jensimmons.bsky.socialWhen the giant pool of money needed someplace new to go in 2008. It came for us.
www.thisamericanlife.org/355/the-gian...
en.wikipedia.org/wiki/The_Gia...
@jensimmons.bsky.socialYes, that's what I'm working on. How list boxes & mutliselect should work in appearance: base. We have a chance to hit the reset button & make something that works well going forward. It will definitely include the ability to style everything.
@jensimmons.bsky.social* not <select id="foobar" multiple item="6"> It’s <select id="foobar" multiple size="6"> Ouch!! That's how little the existing HTML makes sense to me. Feels so 1994.
@jensimmons.bsky.socialOh it is size! I mistyped.
@jensimmons.bsky.socialDo you make websites? What do you wish <select> listbox did? Or didn’t do? This is the HTML. Currently, it automatically creates a listbox with 4 options showing. <select id="foobar" multiple> If you want 6 items showing, you write <select id="foobar" multiple item="6">. What should it be?
@jensimmons.bsky.socialAssuming the quality efforts that went into Safari 26.4, 26.5, 27.0 were some kind of one-and-done project? Nope! Just look at all the improvements in Safari Technology Preview 253.
@jensimmons.bsky.socialThis particular demo doesn’t seem to work when the device is turned & folded (partically) in a “laptop” posture. But that’s just this demo. Others work great.
@jensimmons.bsky.socialIt is available! It’s at Users & Access > Xcode Cloud > Safari Web Extension Packager.
@jensimmons.bsky.socialYes to both. They are defined in API called Device Posture & Viewport Segments, and are supported in Safari 27.1 beta behind a flag. To turn them on in the simulator for iPhone Duo (available with Xcode 27.1 beta), go to Settings > Apps > Safari > Advanced > Feature Flags and enable each.
@jensimmons.bsky.socialYes, Safari 27.1 beta supports both Device Posture & Viewport Segments API behind a flag. To turn them on in the simulator for iPhone Duo (available with Xcode 27.1 beta), go to Settings > Apps > Safari > Advanced > Feature Flags and enable each.