2017-08-31 1:38 GMT+02:00 Pete d'Oronzio <
pe...@pdmagic.com>:
> My main goal is to find some newgroup or other forum where asking
> questions like "which browsers will work for x, and which don't", or
> "why doesn't this work in Edge" is acceptable. I would imagine that
> asking that here would result in a response like "this group is for FF".
>
Definitely a good place to discuss spec implementation inconsistencies…
especially within Firefox ;)
Thanks, it make things a bit easier to understand. That example is still
somewhat heavy but it is enough to speculate that there is something wrong
with your code at some point.
I did a quick experiment about hovering a <g> element to have css rules
applied to children and it works fine in all browsers I've been able to
test with (namely: Firefox, Chrome and Safari):
-
https://jsfiddle.net/JeremiePat/3j0thakv/
Based on that and as it seams to match your use case, I suggest that you
spend some time in your code to try to spot in what way is your code
handling that to see what makes Chrome behave differently than Firefox as
they shouldn't in that case of hovering g elements. My suggestion is to
take the example you provide and try removing things one at the time until
the hovering behavior occurs in at least 2 browsers, meaning the last piece
you removed is likely the cause of that different behavior.
Best,