You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Good point, I was thinking about something similar today. Technically we want to offer a quick glimpse into the main principle of the library, give the user a feeling what the tool is about. The static site so far demos the UI, but after accepting all test cases there's no way to play around and "fail" a test. We would want to offer the user a way of meddling with the HTML.
One solution for handling this in-page could be by maybe storing the edited HTML into local storage for the test page to pick up?
Any other ideas? Do you feel you have time to come up with something small?
Local storage sounds like a good idea. I think having buttons to put it in
various states with a live editable view of the HTML/CSS would be good.
I may be able to look at this before the new year.
On Dec 9, 2015 4:47 PM, "Christoph Burgmer" notifications@github.com
wrote:
Good point, I was thinking about something similar today. Technically we
want to offer a quick glimpse into the main principle of the library, give
the user a feeling what the tool is about. The static site so far demos the
UI, but after accepting all test cases there's no way to play around and
"fail" a test. We would want to offer the user a way of meddling with the
HTML.
One solution for handling this in-page could be by maybe storing the
edited HTML into local storage for the test page to pick up?
Any other ideas? Do you feel you have time to come up with something small?
—
Reply to this email directly or view it on GitHub #72 (comment).
The runnable instance link in the readme shows a 520 error. Could it be replaced with a simpler demo using static files hosted on github?
The text was updated successfully, but these errors were encountered: