This site will have limited functionality while we undergo maintenance to improve your experience. If an article doesn't solve your issue and you want to ask a question, we have our support community waiting to help you at @FirefoxSupport on Twitter and/r/firefox on Reddit.

Search Support

Avoid support scams. We will never ask you to call or text a phone number or share personal information. Please report suspicious activity using the “Report Abuse” option.

Learn More

I accidentally edited something with inspect element, and now this cursor keeps binking on every page I go. How do I undo what I did and get rid of this thing?

more options

what the title says

what the title says
Attached screenshots

Chosen solution

You may have switched on caret browsing. You can toggle caret browsing off/on by pressing F7 (Mac: fn+F7).

  • Settings -> General -> Browsing
    remove checkmark: [ ] "Always use the cursor keys to navigate within pages"

Note that this is a Firefox accessibility feature.

Read this answer in context 👍 0

All Replies (5)

more options

Have you restarted Firefox since? As for as I know such changes are temporary.

Helpful?

more options

thepillenwerfer said

Have you restarted Firefox since? As for as I know such changes are temporary.

yep, i've reinstalled firefox multiple times due to other issues, but it never went away

Helpful?

more options

update: started using firefox nightly and the same issue persisted

Helpful?

more options

Chosen Solution

You may have switched on caret browsing. You can toggle caret browsing off/on by pressing F7 (Mac: fn+F7).

  • Settings -> General -> Browsing
    remove checkmark: [ ] "Always use the cursor keys to navigate within pages"

Note that this is a Firefox accessibility feature.

Helpful?

more options

cor-el said

You may have switched on caret browsing. You can toggle caret browsing off/on by pressing F7 (Mac: fn+F7).
  • Settings -> General -> Browsing
    remove checkmark: [ ] "Always use the cursor keys to navigate within pages"
Note that this is a Firefox accessibility feature.

It worked... thank you!!!

Helpful?

Ask a question

You must log in to your account to reply to posts. Please start a new question, if you do not have an account yet.