aboutsummaryrefslogtreecommitdiff
path: root/html/tracks.html
diff options
context:
space:
mode:
authorSimon Tatham <anakin@pobox.com>2017-04-26 14:39:45 +0100
committerSimon Tatham <anakin@pobox.com>2017-04-26 21:48:11 +0100
commitbc2c1f69fddac3a51d086fb379f0ec8954f4b894 (patch)
tree9e7d20313a58b4101271b91f8f0d7e6c493e32e8 /html/tracks.html
parentce6e3df99bc7825d1c1638d378320375eb05fd0b (diff)
downloadpuzzles-bc2c1f69fddac3a51d086fb379f0ec8954f4b894.zip
puzzles-bc2c1f69fddac3a51d086fb379f0ec8954f4b894.tar.gz
puzzles-bc2c1f69fddac3a51d086fb379f0ec8954f4b894.tar.bz2
puzzles-bc2c1f69fddac3a51d086fb379f0ec8954f4b894.tar.xz
Javascript puzzles: switch to a CSS-based drop-down system.
The previous control buttons and dropdowns based on form elements were always a bit ugly: partly in a purely visual sense, and partly because of the nasty bodge I had to do with splitting the usual 'Custom' game type menu item into two (to get round the fact that if an element of a <select> is already selected, browsers won't send an event when it's re-selected). Also, I'm about to want to introduce hierarchical submenus in the Type menu, and <select> doesn't support that at all. So here's a replacement system which does everything by CSS properties, including the popping-up of menus when the mouse moves over their parent menu item. (Thanks to the Internet in general for showing me how that trick is done.)
Diffstat (limited to 'html/tracks.html')
0 files changed, 0 insertions, 0 deletions