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.

Sign up for GitHub

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

Jump to bottom

Wrong domain matching for second-level domains #263

Open
zmilonas opened this issue Oct 4, 2018 · 0 comments
Open

Wrong domain matching for second-level domains #263

zmilonas opened this issue Oct 4, 2018 · 0 comments
Labels
bug

Comments

@zmilonas
Copy link
Collaborator

zmilonas commented Oct 4, 2018

Bug report

I only describe experience as a user, I haven't had the time to look at the code

Steps to reproduce - current behaviour

  1. I go to a subdomain on a second-level domain website (2LD) - sub.example.org.pl
  2. I open Tusk to autofill
  3. I have an entry for example.org.pl
  4. Matches shown are for all entries that match the 2LD itself

What is the expected behaviour

Matches would be shown for the domain correctly

Additional remarks

Example:

  1. I go to login.university.edu.pl
  2. I see matches for edu.pl
  3. I want to see matches for university.edu.pl

Environment

Operating System: N/A

Browser vendor and version: N/A

Storage Provider: N/A
@zmilonas zmilonas added the bug label Oct 4, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
bug
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@zmilonas