Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Allow specific web pages to opt out of autocomplete #31

Closed
hatemhosny opened this issue Aug 18, 2023 · 1 comment · Fixed by #32
Closed

Allow specific web pages to opt out of autocomplete #31

hatemhosny opened this issue Aug 18, 2023 · 1 comment · Fixed by #32

Comments

@hatemhosny
Copy link
Contributor

Although the autocomplete feature is of great help, some websites might not want their users to use it in specific web pages.

Example:
if a user uses autocomplete superpowers in websites like codewars, leetcode or LiveCodes code challenges (specially if the time factor is important), it might be considered as cheating :)
However, if the same website uses the editor in code tutorials, it might be desirable to enable the autocomplete.

My suggestion:

If a web page includes this meta tag, the autocomplete should not be activated in this specific web page even if the domain is in the allowlist:

<meta name="codeium:type" content="none">

I expect if site owners have control over when to enable/disable the autocomplete, more websites are more likely to endorse it and tell the users about it (even as a feature).

If you agree to this approach, I can open a PR with the implementation, including the option to restrict injection type by the value of the content attribute as mentioned here: #29 (review)

@pqn
Copy link
Contributor

pqn commented Aug 18, 2023

This seems reasonable. I think the additional use case is for our first party partners, we would want to disable the Chrome extension automatically, since they have their own integration.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants