7 ms·

Firefox 130 for Developers

• eimrine 2y ago
  I would like to see all that "Firefox bugs" someone on the page but without extra clicking.
  • bsmth 2y ago
    Heya, MDN technical writer here. Do you want to share a little more details about what you expect to see on the page? Thanks!
    • eimrine 2y ago
      Well, this is not a writing issue but a web-design one. I am trying to read all release notes for all programs I use, it is relatively easy because I am almost cold turkey for FOSS. But reading the MDN page gives me the impression that a lot of browser features derives from some bugs in bugzilla. What I can see from bugzilla is a lot of links but I would like to see either the headers of the bugs, such as implement <details name=""> attribute (exclusive accordion) or the Wikipedia-style cloud with info which appears on hovering the link by the cursor - instead of Firefox bug 1856460 . I understand that developers are familiar with the bugs to that extent they sometimes know what is what by pure number, but the release notes is published not only for developers but also for laymen.
      • bsmth 2y ago
        I understand, thanks a lot for the context. The bug titles aren't always very descriptive, so we try to make a good TL;DR on this page. The prose should describe each change as a complete summary of the bug to clarify the practical implications for developers. For instance, "The X interface is now supported, so you can use Y features in Z context.". Ideally, readers shouldn't need to click the Bugzilla link unless they really want to deep-dive into comments or find specific patches. I'll mention this with the team anyway, we're always looking to improve. There may be options like showing a tooltip with the bug title on hover or something similar.
• deleted 2y ago
  [deleted]