Curious, is there a practical reason Ionic UI components start with Ion?

Curious, is there a practical reason for starting Ionic UI components with Ion? Is is just a naming convention, one that is only meant to go along with the Ion(ic) brand or is there something more to it than that?

1 Like

There’s a lot of componentes that if you remove the ion- will coincide with the default HTML elements ion-input, ion-header, ion-footer, ion-img, ion-button

So it’s probably to avoid this kind of conflicts and also to distinguish from other frameworks/tools that may use the same approach.

1 Like

Ah, okay, interesting. Thanks.

Yeah, I was thinking about this only from the mobile side of things so, it didn’t dawn on me that I should also consider the web side of things i.e. components could potentially be clashing with html elements (if I’m understanding you correctly.)

But even in the native part the same apply. Ionic uses HTML, JS and CSS wrapped inside a WebView on mobile, either way the UI is basically a HTML page

1 Like

Ah, right! I was just reading that in this article, in fact:

Capacitor apps for iOS and Android are native apps, they just happen to do a large amount of their work in a primary WebView.

1 Like