Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

WebAssembly Studio

webassembly.studio

Post reply on HN
Print view View original

31–40 of 231 posts

Re: WebAssembly Studio

#31

Post by ratww »

abellerose wrote: post #16
mwcampbell wrote: post #10

The "Create New Project" dialog has serious accessibility problems when used with a screen reader. The buttons are clickable divs, not actual HTML buttons or even marked up with proper ARIA. I haven't yet ventured any further into the app. Given that the app is a WebAssembly development environment, my first guess was that it was built in WebAssembly itself, with a custom UI framework. But in fact, it's plain React,…

..

You can use the ARIA role="button" attribute [1]. You also should make it focusable using tabindex="0" and allow keyboard input, although some screen readers might be able to get around those limitations...

But like another reply mentioned, you can get it all from free using a normal , which isn't really hard to style even compared to a , and provides it all for free...

[1] https://developer.mozilla.org/en-US/docs/Web/Accessibility/A...

Re: WebAssembly Studio

#32

Post by stopyellingatme »

arconis987 wrote: post #9
tomasreimers wrote: post #2

Jokes about the [Birth and Death of JavaScript]( https://www.destroyallsoftware.com/talks/the-birth-and-death... ) aside, I love the concept of WASM and that we're making the web a more robust compile target. One of the big limitations in my mind is that I still don't know of that many people using it in production at scale. Is there a list, or well known set of examples (other than Figma), who are using WASM in prod…

Figma is written in C++, compiled to WebAssembly. Probably the most advanced web-based design tool in the world. I think they have like 4-5M users, and a $2B valuation. https://madewithwebassembly.com/showcase/figma/

Figma is an actual tool, written for the web. Lots of great engineering happening over there.

Re: WebAssembly Studio

#33

Post by mwcampbell »

bavell wrote: post #24
mwcampbell wrote: post #10

The "Create New Project" dialog has serious accessibility problems when used with a screen reader. The buttons are clickable divs, not actual HTML buttons or even marked up with proper ARIA. I haven't yet ventured any further into the app. Given that the app is a WebAssembly development environment, my first guess was that it was built in WebAssembly itself, with a custom UI framework. But in fact, it's plain React,…

I'm guilty of this more often than I should be. I think the reason I sometimes reach for divs over buttons or other semantic elements is because I've been burned by default browser behavior treating them special when I just want a dumb box with a dumb click handler - no default styling that I need to override, no need to call .preventDefault(), no need to worry about the matrix of OS+browser+device that each treats a…

Thanks for sharing your perspective on this.

Does anyone know if the web platform now provides a foolproof way to clear all default styling on a button or other standard control?

Re: WebAssembly Studio

#35

Post by dr-detroit »

Meme technology invented for snowflakes who insist react and angular are replaced by new frameworks every month and therefore web development should resemble 1980s computer science class.

Re: WebAssembly Studio

#36

Post by andrew_ »

bavell wrote: post #4

Seeing gulp being used in the examples for the build step is strange... I wonder why it was chosen. Nothing wrong with it per se but gives me flashbacks to the horrors of my past exposure to it as an inexperienced webdev.

I'd bet this was a "I already know this" decision, even as unnecessary as it is. I find it more bizarre that the tooling is written in TS, the WebAssembly source is Rust/C, and the test use file is plain JS. Some serious language personality disorder there. Some continuity would aid the DX here.

Re: WebAssembly Studio

#37

Post by crisnoble »

mwcampbell wrote: post #33
bavell wrote: post #24

Earlier quoted context omitted.

I'm guilty of this more often than I should be. I think the reason I sometimes reach for divs over buttons or other semantic elements is because I've been burned by default browser behavior treating them special when I just want a dumb box with a dumb click handler - no default styling that I need to override, no need to call .preventDefault(), no need to worry about the matrix of OS+browser+device that each treats a…

Thanks for sharing your perspective on this. Does anyone know if the web platform now provides a foolproof way to clear all default styling on a button or other standard control?

`appearance: none;` gets you a long way

Re: WebAssembly Studio

#38

Post by mwcampbell »

abellerose wrote: post #16
mwcampbell wrote: post #10

The "Create New Project" dialog has serious accessibility problems when used with a screen reader. The buttons are clickable divs, not actual HTML buttons or even marked up with proper ARIA. I haven't yet ventured any further into the app. Given that the app is a WebAssembly development environment, my first guess was that it was built in WebAssembly itself, with a custom UI framework. But in fact, it's plain React,…

..

I'm sorry if I made you feel that you should be ashamed of your lack of knowledge in this particular area. That wasn't my point at all. I'm just sad that we accessibility advocates have somehow not yet been able to reach you and other developers. I'm sorry you felt the need to retract your comment.

Re: WebAssembly Studio

#39

Post by kowsheek »

tomasreimers wrote: post #2

Jokes about the [Birth and Death of JavaScript]( https://www.destroyallsoftware.com/talks/the-birth-and-death... ) aside, I love the concept of WASM and that we're making the web a more robust compile target. One of the big limitations in my mind is that I still don't know of that many people using it in production at scale. Is there a list, or well known set of examples (other than Figma), who are using WASM in prod…

We release a web-based ray tracer built with WASM that's integrated into our existing 3D/AR/VR platform: https://twitter.com/ksqio/status/1334962197324320768?s=20

Re: WebAssembly Studio

#40

Post by no_wizard »

mwcampbell wrote: post #33
bavell wrote: post #24

Earlier quoted context omitted.

I'm guilty of this more often than I should be. I think the reason I sometimes reach for divs over buttons or other semantic elements is because I've been burned by default browser behavior treating them special when I just want a dumb box with a dumb click handler - no default styling that I need to override, no need to call .preventDefault(), no need to worry about the matrix of OS+browser+device that each treats a…

Thanks for sharing your perspective on this. Does anyone know if the web platform now provides a foolproof way to clear all default styling on a button or other standard control?

Yes. This is a good article from CSS Tricks on the subject matter, which describes it all better than I could.

https://css-tricks.com/custom-styling-form-inputs-with-moder...

Post reply on HN