Michał Gołębiowski-Owczarek

Thanks for the report. jQuery traverses `form.elements`, reading values from each entry. Unfortunately, for a Web Component, reading the `value` property won't help. Is there a way to read submitted...

MutationObserver API would catch all the mutations, not just jQuery-managed ones. The solution we agreed on during the meeting, as Timmy mentioned, is to get rid of `getElementsByTagName` from the...

@srushti-learner sure, feel free to try! Let us know if you have questions.

@minami-akira we don’t need to set a formal assignee, feel free to work on it & to submit a PR when ready. Please also read https://contribute.jquery.org/commits-and-pull-requests/ for guidelines.

@melloware Sizzle supports and will support Edge Legacy. That said, Sizzle is getting close to being archived; jQuery 4.0 will embed a selector engine ported from Sizzle with workarounds for...

jQuery version of this issue: https://github.com/jquery/jquery/issues/4109

> Complete the installation process by pointing your browser at http://vagrant.jquery.com/ OK, apparently I'm blind. I'll leave it to you to decide if it should be highlighted more visibly or...

> so that there's not a massive block of expected output before the next (important) step. Yeah, that is most likely what made me jump too far into the list.

Also, note that just defining a policy & using it still won't solve all the issues. You can declare in CSP that you not only want to enforce trusted types...

@tosmolka To be honest, their approach of forking Sizzle makes sense for their use case. We're going to archive Sizzle soon and jQuery 3.7.0 & newer will have their own...