* Next Version ** Use standard Unicode codepoints for icon fonts This is done via the [[https://korewanetadesu.com/pages/fontstandard.html][Font Standard]] icon font. ** Sped up background and book noise animations ** Cat paws ** DONE Migrate to nw.js (from node-webkit) ** DONE Safari 8 / iOS 8 support This is the first version to support Safari on Mac OS X and iOS. The primary problem in earlier versions appears to be a bug in Safari's JIT when optimizing functions that modify JavaScript's ~arguments~ object. Code triggering this bug was rewritten to avoid modifying ~arguments~. This bug is further described in https://korewanetadesu.com/safari-jit-bug.html and seems to still exist in current versions of WebKit's new "FTL" JIT. Prior to OS X 10.10, Safari on OS X will show [[https://bugs.webkit.org/show_bug.cgi?id=134854][artifacts on HiDPI ("Retina") screens due to a bug in its compositing]]. * v1.2 ** DONE Override the GPU blacklist on GNU/Linux This is a security measure Chromium enables for normal web browsing, but it's not needed for a local application. ** DONE Better error reporting Error reporting now includes links to the [[https://yukkurigames.com/support.html][Yukkuri Games support page]] and our email address, and a way to open the [[chrome://gpu]] information pane. * v1.1 ** DONE Upgrade node-webkit wrapper to 0.10.4 This moves the Windows version of Chromium several steps forward, and fixes the stall that prevented the 0.10.x series from working properly on Windows before. ** DONE Close buttons don't scroll off the top of the dialog Actually, they still do in most browsers, but as position: sticky support rolls out, they will work correctly. ** DONE Include DLLs necessary for broader Windows support ** DONE Fix version number in OS X About dialog * Open Issues ** TODO Choppy / staticy audio on iOS Especially when backgrounding, e.g. switching tabs. There's probably no easy way to avoid this. ** TODO Scrolling is broken in licensing window This began when upgrading to nw.js 0.12 (from node-webkit 0.10.4). If it's broken one place it's probably broken other places also. Not reproducible in Chrome 42, so it's possible this was some transient Chromium bug that will be gone in newer NW.js.