- From: Tab Atkins Jr. <jackalmage@gmail.com>
- Date: Thu, 23 Jul 2015 13:39:48 -0700
- To: Sebastian Zartner <sebastianzartner@gmail.com>
- Cc: Rafal Pietrak <rafal@ztk-rp.eu>, www-style list <www-style@w3.org>
On Thu, Jul 23, 2015 at 6:20 AM, Sebastian Zartner <sebastianzartner@gmail.com> wrote: > On 19 July 2015 at 08:06, Rafal Pietrak <rafal@ztk-rp.eu> wrote: >> Hello All, >> >> My first shot at implementation of "a certain" context menu, which shows >> up in a table when mouse ":hover" over its row (or ".click()" on that >> row for mobile devices) is here: (https://jsfiddle.net/fexp/pd6ygatx/7/). >> >> Unfortunately it is rendered differently on chromium, and on >> icewheasel(mozilla) and on www-browser (all that on debian-8.1/jessie). >> >> My goal is to have the context menu look like the imeplementation >> icewheasle presents, that is "follow the mouse". But: >> >> 1. I'm not quite sure which one is actually following the semantics of >> CSS specs. Pls advice is icewheasle/mozilla have it right (and thus will >> stay and will proliferate to others) >> 2. and since only one of them can be right, the others are wrong ... so >> I'd like to notify respective develoers here (google, mozilla, etc; >> which I understand frequent this list) of this bug in their >> implementations; although I con't actually know which one is wrong. > > Here's a simplified version of RafaĆ's example: > > https://jsfiddle.net/g9zp6psj/1/ > > So it looks like Gecko considers relative positioning of table rows > while Blink and Trident don't. Both behaviors are allowed by CSS 2.1, unfortunately. ~TJ
Received on Thursday, 23 July 2015 20:40:39 UTC