You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Type <C-e> to open firenvim in page github.com/glacambre/firenvim/issues/ISSUE_NUMBERS to edit comment / post new comment
What happened
No window was open. Then, I typed <C-e> again, a firenvim window appeared at the upper left corner of the page. The filename contains selector TEXTAREA-id-feedback.
I tried to exclude the element, but the following config did not work:
This is not a bug but the intended behavior, as this enables using Firenvim on elements whose selector cannot be decided. I can see how the behavior you expected is useful though, I'll try to implement it.
xudyang1
changed the title
BUG: unable to exclude some element in github.com
[feature]: extend selector's behavior to choose elements
May 7, 2024
This is not a bug but the intended behavior, as this enables using Firenvim on elements whose selector cannot be decided. I can see how the behavior you expected is useful though, I'll try to implement it.
What I tried to do
Type
<C-e>
to open firenvim in pagegithub.com/glacambre/firenvim/issues/ISSUE_NUMBERS
to edit comment / post new commentWhat happened
No window was open. Then, I typed
<C-e>
again, a firenvim window appeared at the upper left corner of the page. The filename contains selectorTEXTAREA-id-feedback
.I tried to exclude the element, but the following config did not work:
Current solution is to manually click at the comment textarea and then type
<C-e>
to trigger firenvim.The text was updated successfully, but these errors were encountered: