Last modified: 2014-10-03 21:07:25 UTC
See [[User:This, that and the other/sandbox/VE4#columns-list]].
In Firefox the text is overlapped; in Chrome it is worse - the template appears blank, and when you click on it, you get a weird transverse selection box.
*** Bug 50267 has been marked as a duplicate of this bug. ***
(In reply to comment #1) > In Firefox the text is overlapped; in Chrome it is worse - the template > appears blank This part is now working fine. > in Chrome , when you click on it, you get a weird transverse selection box. This is still a problem.
The transverse selection "just happens" to be the width of one column and the height that the text would take if it were not split into columns. The problem may be in the template. A similar problem was found to be due to someone starting a set of columns with {{multicol}} but finishing it with {{col-end}} (rather than properly closing it with {{multicol-end}}). This {{columns-list}} template appears to be a wrapper for {{div col}}, but has no {{div col end}}.
Was about to report a similar bug for another template. Narrowed it down to the CSS property "column-count". It's not specific to templates (though unlikely to appear in nodes other than transclusion nodes right now). Basically the different boundary rectangles we get from the browser for these kind of elements also seem to include a bad layer. That bad layer is horizontally centred and in the shape of how the contents would be were it divided into columns.
Created attachment 15825 [details] Screenshot of typical two-column reflist highlighted in Chrome
Created attachment 15826 [details] Screenshot of case with more than 2 columns In this case it's even more problematic as the column is quite narrow (the width of an individual column) and expands both ways. Thus the "top right corner" where the context menu is, can be offscreen (higher up on the page). In the screenshot I scrolled up so that it is just about visible, but this wouldn't be the case for a regular user.
This is clearly a browser bug, will file upstream, but we may have to find a workaround.
Upstream: https://code.google.com/p/chromium/issues/detail?id=391271
*** Bug 71625 has been marked as a duplicate of this bug. ***
