Possibility to ‘blacklist’ some websites?

[matguidi]

Background

Given the differences in how text entering fields are managed on different website, the extension works flawlessly in some sites while it doesn’t work in others.

Proposed solution

Would it be possible to “blacklist” sites on which we don’t want the extension to be activated? I have searched for such options but it doesn’t seem to be there

Alternative

Alternatively, it would be useful if it were possible to pin the extension button the Firefox toolbar. This would allow users to easily “turn it off” when one wants to compose text on, say, Twitter.

Thanks a lot for making such a helpful extension anyway, I hope you keep developing it!

[rugk]

Duplicate of #35

[rugk]

Though the alternative idea sounds nice? @tdulcet

[tdulcet]

Yeah, adding a page action icon to temporally enable/disable the autocorrection could be a workaround, but a better solution would of course be to fix those remaining issues that prevent the autocorrection from working on all websites. For this, we might need to wait for new web APIs, see #4 (comment) for example. We should probably file a feature request on BMO as well.

Another alternative might be to disable the autocorrection in contentEditable elements by default (where all the known issues occur), but enable it in input and textarea elements.

[matguidi]

Could the last suggestion be a “quick and dirty” fix while we wait for a more elegant solution? I’d be in favour of that, as I’m not familiar enough with html coding to implement something like what you suggest here.

[tdulcet]

Could the last suggestion be a “quick and dirty” fix while we wait for a more elegant solution?

You mean disable the autocorrection in contentEditable elements by default, but enable it in input and textarea elements. That is definitely something we can consider for a future update, although I am not sure most users understand the difference between these elements. Pull requests are always welcome though.