David Arenas

I'm wondering if you would accept a pull request for solving this particular issue, and maybe in the future for other possible cases that may come up. The whole list...

@andrejewski I tried to make it work using the workaround, but it's still not working. Looking at the code, it seems like the parsing algorithm automatically closes tags that are...

@luisherranz, @SantosGuillamot I just saw this draft PR that seems to have all the tasks completed ― it even has a changeset. Would it make sense to take a look...

After doing some minimal testing, I've noticed that middlewares are registered for each request, again and again. That would be fixed though once we implement https://github.com/frontity/frontity/issues/695. @SantosGuillamot should I mark...

Hey @codemonkeynorth, if you create a PR, could you add `itemID` and `itemRef` as well? That way we would be fixing all the item-related attributes defined in the HTML spec....

@codemonkeynorth, don't worry about e2e testing, you can add some simple checks in this unit test: https://github.com/frontity/frontity/blob/0b28d229b278adf97e6953eabb156d0922ba5cac/packages/html2react/src/libraries/__tests__/parse.tests.ts#L19-L28 About running e2e tests on Windows, could you please share the error you...

Yes, it is! I guess we forgot about it because I started it but it wasn't added to the sprint.

I would have to take a look at this, it seems that almost all the work is already done. :thinking:

Hey @felixarntz, thanks for raising this up! 😊 I'm unsure what would be the "best path" (maybe @gziolo could help), but as this tracking issue is meant to be flexible,...

I've added two PRs to the description above. - https://github.com/WordPress/gutenberg/pull/60661 - https://github.com/WordPress/gutenberg/pull/60670 The first one could be considered a bug fix (I've added it under that category), and so be...