Many people use it through Spring Security or Pac4j but the lib is relatively easy to use directly (particularly if you know the protocols) and can be used to add OIDC support to Java apps with much less complexity than those Spring or Pac4j authentication frameworks (but at the cost of having to handle some of the Web security yourself, mainly around CSRF)
Yesterday I was at a restaurant with this artwork on the wall. Can you find the three films whose posters were used here? (hint: two of them are french)
Announcing Platformer: a set of libraries to help implement:
• attribute reflection in web components following the HTML specification
• WebIDL type coercions for your public JS APIs (including web component properties)
@tbroyer love love love this work! Reading the associated blog post you say: Overall, I feel like, as far as primitive/simple types are concerned, boolean, integers, double (not float), string (WebIDL's DOMString), and enumerations are all that's needed
Does this library reflect that belief on what is implemented? If not what heuristic does it use to draw the line of what behavior is implemented?
Sorry if this explained somewhere feel free to link me if so 😅
@haydencodes Ha good point, but no, it implements all numeric and string types of WebIDL, as well as "less common" types like symbol or bigint. I thought about classifying them into distinct files to reflect that opinion (and possibly cut some bytes, depending on tooling) but haven't yet. This is still something I'm contemplating but… naming is hard 😄
I think I totally forgot what React Compiler and Offscreen API are. Majority of the rest has already been seen in Next.js, but I have to admit I never really understood what "transitions" are and how to use them (that said, I haven't coded with React for months). Appreciate the small note on web components support, at last!
It's really clear though that what once was a rather "simple" library (functions returning virtual dom; even the magic of hooks wasn't too hard to grok) has become something really really complex over time.
but sent from an indian investment firm (with valid SPF, DKIM and DMARC, so probably a vulnerable/misconfigured SMTP server on their end);
call-to-action links to the canadian "bikers against pedophiles"' (‽) staging website (a page under wp-includes, so probably leveraging a WordPress vulnerability)
that redirects to a page on the czech Pandora website
that mimics the UAE bank, asking for credit card details (phishing page has already been removed and I forgot taking a screenshot a few hours ago)
For those interested, I just published on GitHub a series of tests for reflecting attributes in web components (see https://blog.ltgt.net/web-component-properties/ for the rationale, I'll update it soon following those tests), reusing the same tests as used by browsers for built-in elements.
Tests include (for now) vanilla custom elements and Lit custom elements.
@sergi@mw I think you're reading too much into my message. My point is that DELETE /a with, say, a body like foo=bar still says "delete /a"; and DELETE /a?foo=bar has a different meaning.
And if you want to say "delete some data that matches foo=bar" then you'd better send a POST (if that "some data" is accessible at /a?foo=bar, then a DELETE there is ok though).
My point, really, is that if you're discussing this then you don't really understand REST and HTTP: what resources are, etc.
I didn't plan that for the same day as Interop 2024, but I just filed bugs to WebKit, Firefox and Chromium on their handling of attributes/properties of type "double" (attributes of the progress and meter elements), and to Web Platform Tests that didn't actually have tests for those (issue filed yesterday, PR sent today):
TIL about git add -N for when I want to start tracking files but only want to include part of their content in the commit:
git add -N file.txt
git add -p file.txt
(I actually generally use git citool rather than git add -p, but the result is the same: you can now add only parts of the file, rather than an all-or-nothing)
I switched my blog https://blog.ltgt.net to @eleventy
3 alpha and ESM.
Saying it was straightforward would be an understatement (or overstatement? 😅 depends how you read that; couldn't be easier and in my case could probably have been automated).