2.5.1 (2019-01-19)
- UI: Add help and preferences links to GUIs (#253) (da628f9), closes #250
- UI: Clarify and clean up styles (#254) (61109fa)
- Change "show all landmarks" key to avoid Firefox clash (#256) (8d73dbd), closes #251
2.5.0 (2019-01-14)
- build: Remove spurious .eslintrc.json from build and zip (#242) (586bf90)
- UI: Message consistency, visual text spacing, visual note spacing (#247) (8c308af)
- Adopt conventional changelog and npm version scripts (#239) (f5e0b39)
- Make the whole build process synchronous (#241) (1c81099)
- Help: Describe new features; heading case consistency (#248) (85c9659)
- README: Fix typo; clarity and style improvements (#240) (9968507), closes #232
- Enhanced help documentation, bundled with the extension (#237) (a8be495)
- toggle: Show all landmarks keyboard shortcut (#245) (10691ee), closes #165
- toggle: Show all landmarks UI (#246) (0803ed7), closes #120
- Improve the appearance of the DevTools panel on Firefox. [#217]
- Fix a bug whereby landmark updates for background tabs pages would show up in the pop-up if it's open. [#216]
- Improve the profiling script considerably, and use the results to improve performance of landmark finding. [#220]
- Fewer debug-mode log messages; tidy up metadata and improve screengrabs; bump dependencies. [#218]
- Make the preferences/options UI clearer and more accessible; improve documentation and metadata; improve build robustosity. [#228]
- Fix a bug with sidebar option initialisation. [#213]
- Fix a bug with packaging that was causing the DevTools panel script to be left out of the zip file that gets uploaded to the browser add-on sites (oops again ;-)). [#212]
- Offer an optional sidebar as well as the toolbar pop-up on Firefox and Opera. [#188, #199]
- Provide a Developer Tools panel that allows landmark elements to be inspected in the DOM viewer. This also entailed re-writing the internal communications between parts of Landmarks to use ports instead of one-time messages. [#204]
- Show the current keyboard shortcuts on the splash page and allow the user to update them on Chrome and Opera. [#187]
- Fix a bug whereby if an element is removed from the page, its border would remain. Also, update the border if the highlighted element's size or position changes. [#210]
- Massive re-organisation of the code to make it easier to manage and accommodate and take advantage of cross-browser differences. [#191]
- Several smaller code improvements, including: clean-ups to the generated code; efficiency and documentation improvements and new screengrabs and captions. [#207, #209, #211]
- Support multiple labelling elements when
aria-labelledby
is used. [#176] - Keep labels legible, and borders neat, when landmark regions are narrow, or full-width/height. Also let pointer events through the border so the user can interact as normal with the page below. [#179]
- Small refinements to the build process, documentation and error-handling. [#174, #178]
- Add landmark labels to the border, which is now drawn more robustly and has customisable colour. [#158, #162]
- Options are saved as they're changed by the user, and borders get updated to reflect settings changes immediately. [#160]
- Fix text sometimes overflowing buttons in Firefox. [#163]
- Minor tweaks to documentation, build process; library package bumps. [#159, #161, #164]
- Support Digital Publishing ARIA module landmarks, and makes landmark role names friendly and translatable. [#150]
- Always scroll to the top of a landmark when moving to it. [#151]
- Plumbing work on the build system and other code improvements. [#145]
- Improve performance on sites/apps that change rapidly (such as Google Docs) by limiting how quickly Landmarks responds to further changes when they're being made in quick succession. [#139]
- Add a keyboard shortcut to show the landmarks pop-up. [#135]
- Give the options page a title that shows up for Opera users. [#136]
- Behind-the-scenes code and infrastructure improvements for improved quality. [#124, #128, #129, #130, #142, #143]
- Landmarks are now updated when pages change dynamically (not just when the whole page is loaded). This should make the extension much more useful when working with web-apps and pages with pop-ups and slide-out menus, for example. [#111]
- Add a keyboard shortcut to skip to the main landmark. [also #111]
- Fix a bug whereby sibling landmarks may not be identified as such. [#112]
- Adopt more browser-like UI on Firefox (pop-up and options) and Opera (options). [#115]
- Use Mozilla's 'addons-linter' to check the built extension. [err, also #111]
- Landmarks now ignores visually hidden regions. [#85]
- Fix a bug that caused the pop-up to incorrectly report nesting that changes by more than one level between landmarks. [#102]
- Correctly restore elements' outlines after they are highlighted. [#94]
- Automatically disable the extension on browsers' extensions store pages. [#97]
- Start exploring what's needed for Edge support in future. [#99]
- Improvements to the SVG to PNG process. [#95]
- Other more minor tweaks and fixes.
- README updates.
- Officially support Opera.
- Make the landmark highlight more visible.
- Open a help page when the extension is installed/updated on Firefox (this was already supported on Chrome, and is on Opera).
- Make use of Firefox's synching of settings across devices.
- More tests, and numerous other code improvements behind the scenes.
- Partly works on Edge; still a few things to sort out before it's robust (also, the extensions store is not yet immediately open to submissions from allcomers).
- Add a test suite to ensure landmarks are identified correctly.
- Various large internal code-quality improvements.
- No user-facing changes.
- Fix error in packaging (the new build system was not actually compressing the ZIP file, which different parts of the submission process for Chrome and Firefox didn't like—oops!)
- Add more code robustosity checks with ESLint.
- Clean up the appearance of the pop-up.
- Increase 'momentary' highlight duration to two seconds, from one second.
- Remove a workaround for a bug in Firefox pop-up sizing that was fixed in Firefox 50.
- Drop Grunt and switch to just using NPM and scripts for building the extensions.
- Track builds with Travis CI.
- Use ESLint and EditorConfig code standards and quality tools.
- When installed/updated on Chrome, show the web page, with a (hopefully) helpful notice about the install/upgrade.
- Automatically re-inject the content script on Chrome when the extension is updated (or inject it when the extension is installed), as users would expect it to start working straight away. (Firefox does this itself.)
- Locale is now en_GB (instead of en).
- Switch to using grunt-phantom-rasterize for converting the SVGs to PNGs.
- First WebExtension Release