Cossid

Members
 View Profile  See their activity

  • Posts

    11

  • Joined

  • Last visited

Cossid's Achievements

Noob

Noob (1/14)

1

Reputation

  1. Cossid
    Same issue, ipv6 docker containers will not start with `bad argument` error if you have an `--ip6` argument set. Docker itself shows ipv6 info in the docker settings section, but within each container, only the ipv4 subnet is shown. Also rolling back as a result.
  2. Cossid
    Changed Status to Closed
  3. Cossid
    After testing, it does appear to save the order outside of the browser. I still feel this is a bad UI decision, as it's not at all obvious in a case where order actually does matter and is not a preference. At the very least, the lock should be present on the page content itself.
  4. Cossid
    Well, on the Gray theme, it's not a green lock, and it's in the sidebar, and really not obvious. This seems like a bug to me. As I understood it, the lock/sorting was for display purposes, but for docker, it has implications to the containers it's running itself, and isn't something that should be stored at the browser/cookie level.
  5. Cossid
    Unsure if this was present in 6.12.0 or 6.12.1, as I went from 6.11.5 to 6.12.2 On the Docker UI screen, you used to be able to drag and drop (or there was a grabber on each line item) to set a preference for which order your Docker containers booted up. That appears to have regressed in 6.12.2 and is completely missing. I also tried advanced view and multiple browsers (Firefox, Chrome), and there appears to be no way to order docker container startup order anymore. I also tried multiple color themes (black and gray) and they all resulted with lack of ability to change order. This isn't an issue of display order preference, there can be an importance of docker containers being dependent on a correct state of a prior docker container to startup properly.
  6. Cossid
    Changed Status to Closed
  7. Cossid
    Thanks, and just as a note, I edited the original post, this applies to the Azure theme as well. Marking closed.
  8. Cossid
    100.0 is current stable release according to their release page, 101 isn't release tree yet. https://www.mozilla.org/en-US/firefox/releases/ And I honestly think you have something cached, like I did for a while. But it is currently actively broke in rc8 on Firefox when cache is disabled for me.
  9. Cossid started following [6.10.0-rc8] Navbar scroll bar always visible in Firefox
  10. Cossid
    I couldn't find anything searching for scroll, hence the post. Glad it is being addressed. I'm on the latest, 100.0, the issue is Unraid is using a deprecated property value, and upgrading to newer versions won't solve that.
  11. Cossid
    This may have come from an earlier release and css was cached, but it is certainly present in 6.10.0-rc8. css style #nav-block contains the property "overflow-y: scroll;" which on Firefox forces the visibility of a scroll bar. "overflow: -moz-scrollbars-none;" property is also set, but it is discarded as an invalid property value. "overflow: -moz-scrollbars-none;" instead needs to be replaced with "scrollbar-width: none;" to have the desired effect seen in Chrome and other browsers. This is a Firefox-only property and will be discarded in Chrome and other browsers. Edit: Is appears there is an attempted fix in the css that isn't applying, and it's a less optimal fix than scrollbar-width: #nav-block{-ms-overflow-style:none;overflow:-moz-scrollbars-none} #nav-block.mozilla{margin-left:-17px;overflow-y:scroll} the .mozilla class isn't being applied anywhere, and the margin-left is more of a hack than scrollbar-width, as it causes layout shift.. This is currently broken in both Gray and Azure themes.