Bug#838178: tracker.debian.org: "action needed" details show only with Javascript enabled
On Sun, 18 Sep 2016, Thomas Schmitt wrote: > When i discussed the hint on debian-mentors i got the advise to file > a bug because the detail information is supposed to be visible without > toggle if the browser has no Javascript enabled. > https://lists.debian.org/debian-mentors/2016/09/msg00305.html Well, it's visible if you don't have CSS IIRC and as such in text browsers that don't have javascript, it's visible. But if you apply CSS, you get the hidden by default and you need javascript to unhide the folded entry. I'm not sure if we can add CSS that apply only when javascript is disabled... Otherwise, the usual way to deal with that is to put a real link showing the details of the action item on a separate page and add javascript on the onclick that disables the link so that the usual unfold action is executed instead of folling the link. Cheers, -- Raphaël Hertzog ◈ Debian Developer Support Debian LTS: http://www.freexian.com/services/debian-lts.html Learn to master Debian: http://debian-handbook.info/get/
Bug#838178: tracker.debian.org: "action needed" details show only with Javascript enabled
Hi, Raphael Hertzog wrote: > Otherwise, the usual way to deal with that is to put a real link showing > the details of the action item on a separate page That's what i expected naively when the mouseover text told me that details would be available on clicking. I did not get to the idea that Debian's package tracker needed Javascript. Instead i googled and downloaded the 1.9 MB .yaml file of multiarch hinter. Have a nice day :) Thomas
Bug#838178: tracker.debian.org: "action needed" details show only with Javascript enabled
On Mon, 19 Sep 2016, Thomas Schmitt wrote: > That's what i expected naively when the mouseover text told me > that details would be available on clicking. I did not get to the At some point, the chevron was not a real link. But to make it work for screen readers, we had to change it into a "fake" link. Now to make it work for users with javascript disabled we have to change it into a real link... It's not the kind of work that I find really useful/enjoyable. :-| Cheers, -- Raphaël Hertzog ◈ Debian Developer Support Debian LTS: http://www.freexian.com/services/debian-lts.html Learn to master Debian: http://debian-handbook.info/get/
Bug#838178: tracker.debian.org: "action needed" details show only with Javascript enabled
On Mon, Sep 19, 2016 at 2:39 AM, Raphael Hertzog wrote: > On Sun, 18 Sep 2016, Thomas Schmitt wrote: > > When i discussed the hint on debian-mentors i got the advise to file > > a bug because the detail information is supposed to be visible without > > toggle if the browser has no Javascript enabled. > > https://lists.debian.org/debian-mentors/2016/09/msg00305.html > > Well, it's visible if you don't have CSS IIRC and as such in text browsers > that don't have javascript, it's visible. But if you apply CSS, you get > the hidden by default and you need javascript to unhide the folded entry. > > I'm not sure if we can add CSS that apply only when javascript is > disabled... > There are two technical things strategies worth considering here. 1. Use JS to modify the className of the body element One technique for doing this is to use Javsacript, to add/remove a CSS class from the body of the page. For example: https://web-design-weekly.com/snippets/add-class-to-body-f-javascript-is-enabled/ https://css-tricks.com/snippets/javascript/css-for-when-javascript-is-enabled/ You could have the page start out with document.documentElement.className = "js"; And now your CSS rules can switch based on this body class. 2. Create show/hide behavior that relies on CSS, not Javascript For this particular case, a non-JS solution that fits the desired behavior might be something along these lines: http://www.inserthtml.com/2012/04/css-click-states/ For a long discussion of other options that achieve the same thing, see: http://stackoverflow.com/questions/19170781/show-hide-divs-on-click-in-html-and-css-without-jquery If operating without JS is a design goal, but CSS is OK, then these might be a really good fit. If the site's UI needs can be implemented via CSS, then you can provide the dynamic interface you want without having to build two different interfaces or think about fallbacks. Going that route might allow you to skip the BODY class thing. 3. Conclusion I'm hoping that this technical contribution is useful, but I know that I don't have the full context on what everyone here needs, so if not useful, then thanks for reading it anyway! I sympathize with you Raphael when you say it's not the kind of work you find really useful/enjoyable. I surf the web with JS enabled. I think it'd be nice if the non-JS users could submit patches to make sure the app works in their environment. I would find it supremely interesting to have a set of people get together and publish a set of technical suggestions/recommendations for Debian websites, with tricks like the above. That way, the people who want websites to work with JS disabled can do the education work once, and the people building the websites can look at a quick reference and write code that works once without surprises down the road. I can't commit time to that at the moment, but I would attend a sprint, for example.
Bug#838178: tracker.debian.org: "action needed" details show only with Javascript enabled
Hi, i wrote: > > i expected naively Raphael Hertzog wrote: > It's not the kind of work that I find really useful/enjoyable. :-| That's why i make no GUI but rather hide behind a 5000 lines man page. Nobody can claim naivity any more when finally having read up to the description of a feature. Back to topic: Other sites which rely on Javascript simply state this demand. E.g. if the mouseover text had been "Toggle details (Javascript)" then i had mildly muttered but not considered this a problem. Iceweasel can do Javascript, after all. The web is just too annoying when it's enabled. Have a nice day :) Thomas
Bug#838307: qa.debian.org: reports wrong package version in testing
Package: qa.debian.org Severity: important Dear Maintainer, Testing currently contains linux 4.6.4-1 But tracker reports 4.7.2-1 https://packages.qa.debian.org/l/linux.html testing 4.7.2-1 unstable 4.7.4-1 This may mislead package maintainers into believing package in testing is recent when, in reality, testing contains a much older version (with more security issues). Note: New package tracker correctly reports linux version: https://tracker.debian.org/pkg/linux testing: 4.6.4-1 unstable: 4.7.4-1 BR, Franck -- System Information: Debian Release: stretch/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 4.6.0-1-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system)
