Not if the path does not start with webman.

The problem is that the domain can be anything, since synology NAS are
deployed on premises.

Alternative would be to be able to inject the exact URL in an options
pages,  but this was my first contribution to a chrome extension and I
don't know how to do it, or even if it is possible.

Also, this is really mitigated by the fact that, on the highly unlikely
event that one of the existing domain-match has a path starting with
/webman, it should never break it,  since the button will not likely be
matched by the selectors. Both scripts will be injected,  but the ones not
fit will not have any effect.

It was bugging me as well, but I'm afraid that it will be by design.
-----

Small message with lots of typos? Yes, because it was sent from my phone
Le 17 mars 2014 23:54, "hobeone" <notifications@github.com> a écrit :

> In extension/manifest.json:
>
> > @@ -70,6 +70,10 @@
> >      {
> >        "matches": ["*://jamstash.com/*"],
> >        "js": ["shared.js","keysocket-jamstash.js"]
> > +    },
> > +    {
> > +      "matches": ["http://*/webman/*"],
>
> I'm really uncomfortable with the wildcard for the domain. Is there an
> alternative we could use here?
>
> Also, will this take precedence over one of the other matchers?
>
> --
> Reply to this email directly or view it on GitHub<https://github.com/borismus/keysocket/pull/44/files#r10682994>
> .
>