Closed ogallagher closed 4 years ago
This could be done in the reverse direction when navigating too, from the textile page to the home page.
I learned today that cookies are typically limited to 4KB, which is much too small to store puzzle data, whose paths alone are more than 1MB. So for now I will not implement this :L
When the “fullscreen” button is pressed, the textile page is loaded with the puzzle id as a url param, which is used to fetch the puzzle text and shape paths from the server. This could be much sped up if the home page stored the puzzle object as a cookie prior to switching pages, which could then be restored when the textile page loads, instead of reloading the whole puzzle.