WeWeb displays semantic HTML <button> elements as plain text

[rikoentw]

In terms of accessibility, it would be convenient to have an actual html button tag. Since weweb does not offer a button with actual HTML button tags (the weweb buttons use div tags), I thought I might try to create a coded component myself with a HTML template including <button><\button>.

Apparently though, button tags are not rendered/displayed as buttons on a weweb page (inside the editor at least). Neither when importing a coded component, nor when I add a button tag manually into the DOM via the console. I figure there is some preprocessing going on or maybe global css overriding native style, I don’t know. Can you confirm this behavior? And if so, why does weweb not allow/hinder developers to make use of semantic html tags?

It’s also not displayed as expected in HTML components:

[dorilama]

@rikoentw

it would be convenient to have an actual html button tag

you may have missed it but the button element is rendered as a button in the editor when using preview mode and in the final app when you publish.

[archenia_jsanchez]

Can confirm. WeWeb’s nocode button does show up in production as a <button>

tip: you can also control the type if that’s something you need

[rikoentw]

I did miss this, thanks.
So I guess weweb removes the default CSS and applies the weweb button style. Adding style manually worked.

Then I suppose you can also use coded components with <label> etc.