[17:35] <teward> wgrant: has there been any font size changes in the UI for the Overview, Code, Bugs, etc. buttons on pages?
[17:36] <teward> seems to me the font size was reduced (where it is in relation to everything else makes it seem dwarfed and a little more tricky to work with, in my opinion)
[20:12] <wgrant> teward: It hasn't changed at all, just moved. It was always pretty tricky to work with, and I'm very open to suggestions for improving it.
[20:14] <teward> wgrant: +2pt font size on the 'tab bar' is my opinion, i'm just too lazy to write my own userscript to do that XD
[20:14] <teward> i miss the breadcrumb trail too, but i'm glad the bug numbers are back
[20:14] <wgrant> The breadcrumb trail still exists when the rest of the page doesn't duplicate its information.
[20:14] <teward> although the font size for that could do with a small increase too
[20:14] <teward> true, but on bugs in the ubuntu namespace, they're effectively gone, AFAICT
[20:14] <teward> which is fine, i'm happy to snag the bug number from the URL, but meh.
[20:15] <wgrant> The bug number is back now, though.
[20:15] <teward> as i said
[20:15] <teward> grrrr, my VPN is misbehaving, give me 2 minutes to switch to a non-VPN'd connection
[20:15] <wgrant> https://dogfood.paddev.net/ubuntu/+source/apt/+bugs is still running the old code for comparison, by the way.
[20:15] <teward> ack
[20:15] <wgrant> Compare vs https://launchpad.net/ubuntu/+source/apt/+bugs
[20:15] <dobey> eh, the "tabs" seem fine to me
[20:16] <teward> dobey: that's just a minor one, i'm harping on the ease-of-readability now of the bug numbers
[20:16] <teward> smaller and not bold, makes it a little tricky to read on standard res without zooming, at least on this screen
[20:16]  * teward shrugs
[20:17] <dobey> and i'm on a 185 PPI screen, and zoomed out one level :P
[20:17] <wgrant> Ah true, it used to be bold.
[20:17] <dobey> the problem with the bug number display on the bug page for that bug, is that it's quite low contrast
[20:17] <teward> wgrant: and AFAICT maybe a point or two bigger
[20:17] <dobey> as it's gray on white
[20:17] <teward> dobey: true, that's another issue
[20:17] <wgrant> I only stuck the bug number in there because there was no other way to do it without styling changes.
[20:17] <teward> bold or bkacl would be a little better.
[20:17] <teward> s/bkacl/black/
[20:18] <teward> and apparently i need to beat my keyboard into submission again
[20:18] <dobey> at least darker grey would help
[20:18] <wgrant> It should soon be a number next to the summary, like it is in bug listings today, but that requires some minor fixes to the inline title editor.
[20:18] <dobey> oh, that would be beetter, yeah
[20:18] <teward> indeed.
[20:19] <teward> my only last complaint on a bugs page is aesthetics - if you keep 'reported by' that font size looks dwarfed next to the 'person' image next to the name...
[20:19] <teward> might just be because of the size of that image, but...
[20:19] <dobey> my main issue with the current bug # line is the contrast
[20:19] <teward> agreed with dobey, a size increase or a contrast increase (darker gray or black) would fix that
[20:19] <wgrant> The current bug number line is the easiest thing that I could do to fix the regression from hiding the breadcrumbs :)
[20:19] <wgrant> It's very much a this-week solution.
[20:19] <teward> yep
[20:19] <wgrant> Thanks for the feedback.
[20:20] <teward> you're welcome, sorry if i'm harping on the nittygritty tiny things...
[20:20] <dobey> if it's going away in favor of bug # in the summary line, i'm fine with that
[20:20]  * teward has a horrible penchant for doing that
[20:20] <teward> agreed with dobey
[20:20] <wgrant> Nittygritty annoying usability issues are the worst.
[20:20] <teward> heheh
[20:20] <dobey> as the rest of the info is duplicated in the expansion
[20:20] <teward> last question: what's the plan for the "reported by"?  Where will that go whne that line disappears
[20:20] <teward> or is it staying?
[20:21] <dobey> teward: click the arrow next to the project name to expand it
[20:21] <dobey> teward: it's already there :)
[20:21] <dobey> along with confirmed date even
[20:21] <teward> that's... fine, but those of us who use at-a-glance looking have to hunt for it now.
[20:22] <teward> granted, I've started pulling bug data for me to work on via the api, so...
[20:22] <teward> all the data exists in that method :P
[20:22] <dobey> which you have to do anyway, if the bug has multiple projects/packages
[20:22] <teward> mhm
[20:22] <dobey> if you even care about that data
[20:22] <teward> i pull the 'submitted by' in the automated reports that get generated of things in the nginx package on my radar.  the API is a useful tool :)
[20:23] <teward> thanks to you all for the assistance with all that by the way
[20:23] <dobey> i mostly only use it to know who to yell at for filing crappy bug reports :)
[20:23] <teward> heheh
[20:37] <wgrant> No real plans for the "Reported by" line at the moment. Trying to make the header sane so far.
[20:38] <wgrant> But any feedback you have, I'd be glad to hear.
[20:38] <teward> there's probably bound to be more as changes come
[20:38] <wgrant> Starting with making https://dogfood.paddev.net/ubuntu/+source/apt/+bugs not say the package and distro four times in the header each.
[20:41] <dobey> well, if you don't know where you're searching for in that entry box, you can't say we didn't try to tell you
[20:42] <wgrant> Heh
[20:54] <ScottK> wgrant: On that page, I almost always want to sort by date most recently changed and it's annoying I can't.
[20:58] <wgrant> ScottK: You can sort by the shown columns, and select which columns to show, and date_last_updated is shown by default. I suspect you've selected not to show that column in the past.
[20:58] <wgrant> Click the gear in the top left of the table to enable it.
[20:58] <wgrant> (you still can't change the default sort, though)
[20:58] <ScottK> Right.  It's missing from the default.
[20:59] <ScottK> I know how to manage it, but it's annoying.
[21:09] <wgrant> ScottK: Oh, I thought it was in the default. Hm.
[21:09] <ScottK> Don't think so.  I'm on a ~new system where I've never been to dogfood before and I don't see it.