View transitions api, it's pretty new: https://developer.chrome.com/docs/web-platform/view-transiti...

Surprisingly, Firefox of all browsers doesn't support it.

https://caniuse.com/view-transitions

That's a pretty major deal breaker for OP to leave out of his post touting it as something to build everything in your site on (especially for a tech blog)! Does it at least have a polyfill story? I see no mention of how to make it work on, uh, the other 15% of browsers worldwide, CanIUse is telling me.

If you use it in a browser that doesn't support view transitions, the pages just don't animate. no harm no fowl

It's not that surprising if you consider that all the browsers on that page, except for Firefox and Safari, are Chrome-based

Very cool, thanks!

    struct HealthState {
        model: String,
        chat_model: Option<String>,
        device: String,
        arch: String,
        cpu_info: String,
        cpu_count: usize,
        cuda_devices: Vec<String>,
        version: Version,
        webserver: Option<bool>,
    }

https://tabby.tabbyml.com/docs/administration/usage-collecti...

> with WPEngine’s

"WPEngine's" being key here. Some of the banned people are wordpress contributors, unrelated to WPE. The other banned people are not contributors at all and seemingly the only reason they were banned is that matt is angry at their tweets.

You can't cut "WPEngine’s" off from the disjunctive that follows.

> and/or its employees’, users’, customers’, or partners’

That clause is why I discussed the evidence that the people banned seem to me to fall under the meaning of the word partners.

I’ve been deactivated on Slack since very early in this dispute, and later banned from the issue tracker: https://journal.rmccue.io/468/on-contribution/

The only potential cause of this were some posts discussing the arguments behind the original lawsuit - they’re written in my personal capacity, and I’m not a partner of WP Engine. Matt is simply banning anyone who speaks out at all, even when they agree with points he’s made - it’s nothing to do with their partnership status.

(I’m not a WP Engine partner, and my day job is running a competitor to them. Aside from that, I’ve been contributing for 20 years to the project, am a committer, and built several large parts of WordPress including the REST API.)

I find this astounding given your contributions. Feel free not to answer but how is this affecting businesses such as the one you work for? How is the rest of the Wordpress agency/consultancy community reacting to all this? It’s not a space I play in, despite having heavily built on Wordpress in the past (and since abandoned it after this debacle), but I am curious. Are agencies just pretending it isn’t happening? Making contingency plans?

They didn't, they emphasized it.

How do you figure that the people mentioned are partners with an unrelated wordpress hosting platform?

Parters involved in WPEngine so yes, you can cut it off. If they aren’t working on that specifically it’s irrelevant if they’re partners on a separate project, even if it’s similar

None of the banned people mentioned a fork, some don't even have anything to do with wordpress other than commenting about the drama on twitter. The whole post is matt gaslighting to justify the purge.

> None of the banned people mentioned a fork

Steady on, at least one of them wrote a big blog post on his own site Dec 20 basically prematurely accepting the honour.

https://joost.blog/wordpress-leadership/

I can imagine the excessive smugness there about 'taking back the commons' triggered the purge.

It feels very resistant to doing anything other than summarizing. Even when you ask questions for details, the answer is always in the form of a simple summary.

> This was also changed recently in 2010 by adding WAL mode.

2010 is closer to sqlite's creation than today, not very recent

Tried this today and came across an issue that I could not get around: if the dialog contains a form, then submitting the form with enter (focused on any input) or space (focused on the submit button) will close the dialog. I couldn't find any nice way of preventing it.

Normally a form will reload the page anyways so I guess this isn't a normal problem but I was using htmx.

Your last sentence is likely right, by default the form issues a network request.

I've been using a dialog form to update an iframe (it's an editor) so it does work as normal the target iframe gets reloaded. It does not close the dialog though.

I can't produce the case where hitting enter closes the dialog. It should be the same as `<button type='submit'>submit</button>` which also does not close the dialog.

FWIW I learned yesterday that a button _can_ close the dialog:

    <button formmethod="dialog">Update & Close</button>

> Tried this today and came across an issue that I could not get around: if the dialog contains a form, then submitting the form with enter (focused on any input) or space (focused on the submit button) will close the dialog. I couldn't find any nice way of preventing it.

preventDefault and stopPropagation?

There's no event for the dialog about to close, only an event for after the dialog closes. You can prevent default on the enter key and space key, but that obviously breaks the form ux.

There is an event for the dialog about to close from pressing the escape key. No idea why it's only for closing via escape key.

I think they meant prevent the form submission on the `submit` event and use JavaScript to make the submission.

https://developer.mozilla.org/en-US/docs/Learn/Forms/Sending...

I've been seeing more and more sites with a "Subscribe/pay to decline cookies" option

They are making changes that cannot be done or are very difficult with vscode extensions

What might they be? API calls, read all files, write to files, side bar, UI interactions in editor. These are things I would imagine an extension can do. Continue.dev is an example.

The RC for 1.17 is out, and the notes will tell you what type checks are included: https://github.com/elixir-lang/elixir/releases/tag/v1.17.0-r...