Monica Cellio
Monica Cellio
Related: https://github.com/codidact/qpixel/issues/385
It's normal after a refresh. The concern is that if people don't refresh, they're left thinking there was a problem when there actually wasn't.
If we take the flag approach then we need to come up with some baked-in reasons. We're already showing a modal dialogue that people have to click "ok" on; can...
I don't know if baked-in reasons are necessary; I'd rather start with just a textbox and see what patterns arise. And I definitely don't want people to have to go...
Thanks for looking into what screenreaders do with math. That's gotta be a hard problem and now I'm curious.
Oops! That's certainly not intended behavior. We use S3 for our instance but we didn't intend to require any particular shared storage. Thanks for the report.
I'm guessing on the component; @ArtOfCode- can you review and correct if needed?
The reaction model itself enforces "only one", so this isn't just a matter of changing a selector to a multi-selector in the UI. (Hence the "ruby" tag instead of the...
I've seen enough git messes to be concerned about managing multiple suggested edits, yeah. I don't know what the right answer is, but we probably shouldn't allow an edit suggestion...
Yeah, pending edit suggestions aren't very visible, which is why https://github.com/codidact/qpixel/issues/452 is prioritized in the new roadmap. If we make it easier for people to *notice* them then they'll get...