Page MenuHomePhabricator

Timeless has slightly different responsive references CSS vs. Vector (may be due to cascading)
Closed, InvalidPublic

Description

I think it's due to some default of some sort on padding, or possibly that the default column width in Timeless doesn't match that of Vector (or that it does and that because of the 3-column layout it probably shouldn't). If I zoom out from 100% just once with the default widths of a responsive reference list on en.WP, the columns become obvious, so it's clear to me the list is getting the columns styling. It's just that at my default resolution, I almost always have one column where I probably should have two.

(supporting earlier conversation: See thread at my talk page.)

Event Timeline

Izno moved this task from Unsorted backlog to External on the Cite board.
CommunityTechBot renamed this task from j5aaaaaaaa to Timeless missing responsive references CSS.Jul 2 2018, 2:00 PM
CommunityTechBot raised the priority of this task from High to Needs Triage.
CommunityTechBot updated the task description. (Show Details)

I've been musing on this problem and I think it's due to some default of some sort on padding, or possibly that the default column width in Timeless doesn't match that of Vector. If I zoom out from 100% just once with the default widths of a responsive reference list on en.WP, the columns become obvious, so it's clear to me the list is getting the columns styling.

Is there any way to make this sort of styling container-based instead of page-based?

I am not sure what you're asking there.

Izno renamed this task from Timeless missing responsive references CSS to Timeless has slightly different responsive references CSS vs. Vector (may be due to cascading).Jul 31 2019, 7:59 PM
Izno updated the task description. (Show Details)
Izno updated the task description. (Show Details)

I'm not sure what I was asking either, but from some quick testing it looks about the same to me - timeless caps at two reference columns due to the fixed width (and perhaps also the larger font, frankly) and stays at two reference columns even after vector drops down to one for a bit due to losing its sidebar sooner, but the cutoff widths at which this occurs seem consistent between the two in terms of the content itself.

Is there another issue that I'm missing?

Izno closed this task as Invalid.EditedNov 15 2019, 3:49 AM

I don't see the issue any more for some reason. Maybe it was upstream or maybe it was Firefox or the gremlins or... 😃 .