Email or username:

Password:

Forgot your password?
Patrick's posts Back to profile
9 posts total
Patrick Brosset

Today I learned about Object.assign() and how it can make DOM node creation code look a bit more compact:

document.body.appendChild(
Object.assign(document.createElement('div'), {
style: 'color: red;',
className: 'foo bar',
textContent: 'Hello, world!'
})
);

Object.assign(target, source) copies all properties from source to target, and returns target.
developer.mozilla.org/en-US/do

10 December at 8:15 | Open on mas.to
cuan_knaggs
Jan Andrle

@patrickbrosset yes, I use this very frequently, you can define quick helper such as `const el= (tag, idl= null)=> Object.assign(document.createElement(tag), idl);`. There are unfortunately some drawbacks:

- you can use only IDL (developer.mozilla.org/en-US/do)
- `*.append` returns undefined, so it is not easy to create whole template

BTW, I have WIP side-project github.com/jaandrle/deka-dom-e (jaandrle.github.io/deka-dom-el). There is `assing` function (github.com/jaandrle/deka-dom-e) with improvements

@patrickbrosset yes, I use this very frequently, you can define quick helper such as `const el= (tag, idl= null)=> Object.assign(document.createElement(tag), idl);`. There are unfortunately some drawbacks:

- you can use only IDL (developer.mozilla.org/en-US/do)
- `*.append` returns undefined, so it is not easy to create whole template

10 December at 13:23 | Open on fosstodon.org
Patrick Brosset

"web-features" (the thing that powers Baseline) is an awesome open-source project that, with links to other data sources, has the potential of unlocking so many use cases. We're only scratching the surface.

I'm currently mapping web-features to MDN pages. Want to help complete the coverage? See this issue: github.com/web-platform-dx/web

21 November at 20:39 | Open on mas.to
Patrick Brosset

The official results from the State of HTML 2024 survey are now live: 2024.stateofhtml.com/en-US
including a conclusion from yours truly.

The State of HTML logo
13 November at 9:03 | Open on mas.to
Patrick Brosset

Looking at the State of CSS 2024 results. Anchor positioning came out first in the "CSS features you can't use yet" question.

I agree! We can't get this soon enough to get rid of complex and costly tooltip positioning JS code. And, we can all help by applying some pressure!

Firefox implementation bug: bugzilla.mozilla.org/show_bug.
Safari implementation bugs (couldn't find just one parent bug): bugs.webkit.org/buglist.cgi?qu

Vote. CC yourself. Add comments to let your use cases known.

Looking at the State of CSS 2024 results. Anchor positioning came out first in the "CSS features you can't use yet" question.

I agree! We can't get this soon enough to get rid of complex and costly tooltip positioning JS code. And, we can all help by applying some pressure!

Firefox implementation bug: bugzilla.mozilla.org/show_bug.
Safari implementation bugs (couldn't find just one parent bug): bugs.webkit.org/buglist.cgi?qu

7 November at 15:16 | Open on mas.to
Patrick Brosset

Today is the LAST day to submit proposals for the Interop 2025 project.

But also, it's a great time to review the existing proposals and upvote the ones you care about!

Unleash your thumbs-up emojis at:
github.com/web-platform-tests/

9 October at 13:00 | Open on mas.to
W3C Developers

Hear, hear!
@patrickbrosset 👍 👍 👍 !
📢 Submit your ideas for features to become part of the Interop 2025 effort!
▶️ github.com/web-platform-tests/

9 October at 13:31 | Open on w3c.social
Patrick Brosset

The Interop 2025 project is now accepting focus area proposals.

Know of areas of the web platform that could use a boost from the Interop project next year? Submit it at github.com/web-platform-tests/

Want to see what others have proposed, and +1 them? Review the list at github.com/web-platform-tests/

And for more information, read our blog post: blogs.windows.com/msedgedev/20

The Interop 2025 project is now accepting focus area proposals.

Know of areas of the web platform that could use a boost from the Interop project next year? Submit it at github.com/web-platform-tests/

Want to see what others have proposed, and +1 them? Review the list at github.com/web-platform-tests/

17 September at 17:09 | Open on mas.to
W3C Developers

📢 Submit your ideas for features to become part of the Interop 2025 effort!
▶️ github.com/web-platform-tests/

⌛ Interop 2025 is open for proposals until Oct 9th, 2024

If you need some inspiration, check out the Interop 2024 dashboard, which displays feature details, required tasks, and the current scores for each browser.

Interop 2024 dashboard displaying the number of stable features (87 interop and 12 investigations) as of 2 Oct. 2024. Current scores for each browser: Chrome Canary = 99, Edge Dev = 98, Firefox Nightly = 93 and Safary Technology Preview = 95
2 October at 9:14 | Open on w3c.social
Patrick Brosset

🌟 We now have an RSS feed 🌟

You can now subscribe to our web platform release notes at
web-platform-dx.github.io/web-

Thank you @azu_re for contributing that very useful feature.

17 September at 15:56 | Open on mas.to
Patrick Brosset
skryking

@patrickbrosset Nice content. I very much appreciated it, but for some reason the way the paragraphs are broken up made the continuity of thought flow funny. It might just be me though.

4 September at 18:54 | Open on infosec.exchange
Patrick Brosset

Starting with version 128, Chrome and Edge now have an implementation of document.caretPositionFromPoint!

Docs: developer.mozilla.org/en-US/do

Very useful for web text editors, especially when working with Shadow DOM.
This was one of the most requested Chromium features, and was proposed for Interop 24 (sadly not accepted).

We only need Safari now for it to become Baseline!

21 August at 13:55 | Open on mas.to
Go Up