Releases: ueokande/vim-vixen
Release 1.2.4
📔 Other Notes
Search a content from frames successfully loaded (#1418)
By #1099, the console delays completions in asynchronous. It can occur that is input value does not match the displayed completions. It can occur that is input value does not match the displayed completions. For example, the completion item Site A is selected, but the input field shows Site B. The reproduce steps the following:
- Press o to show
:opencommand - Type some keys
- Pres Tab key immediately, before the completions are displayed.
This change awaits fetching completions when users press the Tab key to prevent the issue.
Release 1.2.3
📔 Other Notes
Search a content from frames successfully loaded (#1264)
The previous cross-search tries to all iframe on the page. This can cause an issue "Could not establish connection. Receiving end does not exist." When the browser blocks iframe x-frame options or a content security policy, the background fails to send a message to the frame. This change makes the cross-frame search from frames only successfully loaded and fix #1243.
Release 1.2.2
📈 Enhancement Notes
Cross frame search #1213
This feature allows you to find a keyword over frame and iframes.
Release 1.2.1
Release 1.2.0
📈 Enhancement Notes
Switching to a reader view is now avaiable by gr by
default key settings. For current users, this feature is enabled by adding the
following key-map into your settings:
"gr": { "type": "tabs.reader.toggle" },📔 Other Notes
Improve an error message on invalid settings (#1146)
This change is an improvement when the settings is invalid to identify error
cause. This issue is reported in #722, but it is commonly can be resolved by
restart the browser or clear settings. The issue can still occurs available
when the add-on is updated.
Release 1.1.0
📈 Enhancement Notes
Delay before filling completions (#1099)
Insert a delay before filling completions. When trying opening a new tab or
window using the open command, typing is impaired by the search as you type
functionality, especially if you have a large search base, like long history or
many bookmarks.
Show an error on mark not set (#1104)
If you try to jump to a mark ('a) and the key is not assigned for a mark, the error is shown in the developer console:
"Mark is not set"
but users cannot see that on the page.
By this change, users can see a message on the bottom of the window.
📔 Other Notes
Refactor state management with React Hooks on Console (#1098)
Separate independent states on console state to "completion", "colorscheme", and "app". Each states are managed on Reach Hooks and Custom Hooks wrapping them.
Hide console to focus main window after find executed (#1108)
After error message "Pattern not found: foo" is shown on find mode, the focus
losses from the top window. User cannot do any operation by the keyboard. This
change fixes the focus issue.
This issues is caused by a regression by #1098
Release 1.0.1
Release 1.0.0
From this release, a release versions is named based on semver. The git tag name is "vX.Y.Z" e.g. "v1.2.3".
📈 Enhancement Notes
Iframe dynamic resize (#1034)
Injected iframe to the page is now resized dynamically.
Transparent iframe covering on the whole page used to be inserted before. Although the iframe's style has background-color: unset !important, the page's CSS can overwrite it, and a user saw just a white page.
This change makes iframe follow the content in the console, and it never covers the whole page.
iframe Late injection (#1043)
An iframe for a console is injected to the page only on the addon is enabled. This change minimizes changes for the page user opened.
This PR contains the change in the timing of the initialization in the content-script. The initialization script runs when the document becomes the ready state to reduce the time cannot type keys (this addresses #156, but not perfectly).
📔 Other Notes
Move to GitHub Actions (#957)
Address to error on tabopen command (#1069)
Release 0.32
📈 Enhancement Notes
Check scrollability by actually scrolling elements (#854 by @femnad)
When findScrollable yields no results, check if we can return the current
scrollingElement instead, ignoring doneScrolling check this time. This
fixes the behaviour when it's not possible to scroll up from the bottom of a
page.
Fix "loaded settings are invalid" #919
This addresses an issue the dialog with a message "Loaded settings is invalid"
appeared after Vim-Vixen is installed or restart Firefox. The issue is caused
by injecting an incorrect class to load settings from local.
📔 Other Notes
Update copyright time frame (#909 by @hyiltiz)
Update ScrollPresenter.ts (#913 by @TeepaBlue)
refactor: Make each operation as an operator (#917)
Stabilize NavigationPresenterImpl test (#945)
Release 0.31
📈 Enhancement Notes
Console frame rendering fix (#822 by @dev-output)
Prevents websites from overriding the background and border of the console frame.
Focus inputs without type (#823 by @dev-output)
This addresses issue #779. On the example reported, the input element is
missing a "type" attribute. As per the HTML spec and Mozilla documentation,
this defaults to type="text". It's worth noting that a more spec-compliant
implementation of this feature would be to use a list of input types to not
match, since unknown types (eg. typos) also default to type="text".
📔 Other Notes
Use styled-components instead of vanilla CSS/SCSS in console (#837)
Replace current css/scss code with [styled-components][https://styled-components.com/]
in addon's option page. Styled-components improve on CSS isolation bringing
sustainable code. This patch also includes improving on accessibilities of
components, helping to select element on in e2e test instead of selection by
CSS class name.
Use styled-components instead of vanilla CSS/SCSS in option (#838)
Replace current css/scss code with [styled-components][https://styled-components.com/]
in the console elements. Styled-components improve on CSS isolation bringing
sustainable code. This patch also includes improving on accessibilities of
components, helping to select element on in e2e test instead of selection by
CSS class name.
End-of-support Firefox 68 ESR (#839)
Firefox 68 ESR is no longer supported by Mozilla, officially. This version
became end-of-life on 2020-09-22.
Vim Vixen shifts to Firefox 78 on supported browser version.