Long-time w3m fan, but I have had issues developing for w3m since it doesn’t respect elements such as <main> &  <nav> as block elements ala <div>. An obvious use case is creating a ‘skip link’ for accessibility (created for TUI browsers too!), but when clicking the anchor on a <main id="content"> element, but I get an error `content is not found` for the anchor. IMO this could be broadened so all unknown elements behave like a <div> which matches the spec.
-- 
toastal ไข่ดาว | https://toast.al
PGP: 7944 74b7 d236 dab9 c9ef  e7f9 5cce 6f14 66d4 7c9e

On Wed, Aug 28, 2024 at 11:30:50AM +0000, toastal wrote:
> Long-time w3m fan, but I have had issues developing for w3m since it
> doesn’t respect elements such as <main> &  <nav> as block elements ala
> <div>. An obvious use case is creating a ‘skip link’ for accessibility
> (created for TUI browsers too!), but when clicking the anchor on a
> <main id="content"> element, but I get an error `content is not found`
> for the anchor.

I already have a patch pending which makes w3m recognize <main> and
let's you jump to the line containing <main> with the need for a 'skip
link'. That being said, I agree that making such links work would be a
further improvement for the usability of w3m.

What are the most important tags, besides <main> and <nav>, that need to
be supported?

> IMO this could be broadened so all unknown elements
> behave like a <div> which matches the spec.

Can you point me to the right place in the spec for this? I will see,
how this can be managed. Thanks!