- From: Jake Archibald via GitHub <sysbot+gh@w3.org>
- Date: Mon, 18 Sep 2023 10:36:31 +0000
- To: public-css-archive@w3.org
The problem is, they're not actions. They're just 'tags'. It's down to the developer to decide how they're interpreted on the other side. `action` on a `<form>` determine how the browser 'actions' the submission. [Actions on a notification](https://notifications.spec.whatwg.org/#actions) are turned into buttons for the user to action. Feels like a generic name is better, since there's no policing of what the developer does with these 'tags'. My gut feeling is that the best practice would be for the outgoing page to provide 'information' rather than 'actions', and the incoming page will use this information to determine the action to take. -- GitHub Notification of comment by jakearchibald Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/8960#issuecomment-1723149931 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Monday, 18 September 2023 10:36:33 UTC