On Nov 29, 2017, at 8:27 AM, Martin Gagnon <eme...@gmail.com> wrote:
> 
>> It can be fixed by adding href="#" into the <a> elements
> 
> Using "Inspect" on chrome, I found that adding:
> 
>   cursor: pointer;
> 
> inside "element.style" fix the problem. 

That feels more heavy-handed to me.  My method works with the browser’s 
defaults by giving the anchor tags a target.

Notice that there is no custom cursor attribute on the other <a> tags in the 
menu <div>.  They use href attributes, not onclick, which is why they don’t 
need the cursor attribute to be overridden.

Incidentally, drh, if you ever get around to tightening down the CSP rules on 
Fossil, things like inline onclick=“” attributes can be a problem.  They count 
as inline JavaScript, so are disallowed at the stricter levels of CSP.  For 
much the same reasons as it’s best to move inline CSS out into a separate 
stylesheet, it’s best to move event handler assignments out into an external JS 
file, then arrange for an init function to be called on page load.

Strict CSP can be a pain, alas.
_______________________________________________
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users

Reply via email to