After landing Bug 897160, too wide minimum width of main window so wider min-width. Even if I remove SearchBar, Bookmarks Widget, Download and Home button.

When I open http://www3.nhk.or.jp/netradio/player/index.html?ch=r1&area=osaka There is wasted area when minimize the width.

This minimum width is not enforced on popup windows. It appears that the URL that you linked to was designed to be used within a popup window. How do users reach that page? If the normal way for users to reach that page is to click on a link which opens that page in a popup window, then it should not be cause for concern.

(In reply to Jared Wein [:jaws] from comment #3) How do > users reach that page? I just Bookmarked the URL.

Yes, you may have bookmarked the URL, and other users can get to URLs like that through use of the awesome bar. But pages like that will look awkward unless the user places that URL in a separate window and resized that separate window to the small size that it was designed for. This doesn't seem like a common use case. Either the user would leave that page as another tab in their current window (in which case it would have a lot of blank space before this change), or they would have gone out of their way to separate the tab out in to another window. In the latter case, the user would have extraneous UI elements on the browser window that weren't supposed to be there for the popup it was designed for (in the event that the page has JS that checks window.outerWidth, it will be a taller window than the site may have expected). I think the edge case described by this bug is not worthy enough to remove or decrease the minimum width restriction that bug 897160 introduced.

You can also adjust your bookmark to open the page in the Sidebar, which should satisfy your desires.

(In reply to Jared Wein [:jaws] from comment #5) > Yes, you may have bookmarked the URL, and other users can get to URLs like > that through use of the awesome bar. But pages like that will look awkward > unless the user places that URL in a separate window and resized that > separate window to the small size that it was designed for. > > This doesn't seem like a common use case. Either the user would leave that > page as another tab in their current window (in which case it would have a > lot of blank space before this change), or they would have gone out of their > way to separate the tab out in to another window. In the latter case, the > user would have extraneous UI elements on the browser window that weren't > supposed to be there for the popup it was designed for (in the event that > the page has JS that checks window.outerWidth, it will be a taller window > than the site may have expected). > I mentioned URL for an example. So, As for your description, I do not have a meaning. > I think the edge case described by this bug is not worthy enough to remove > or decrease the minimum width restriction that bug 897160 introduced. No. I think the width restriction may affect any page. It depend on web designer. (In reply to Jared Wein [:jaws] from comment #6) > You can also adjust your bookmark to open the page in the Sidebar, which > should satisfy your desires. when I open Bookmarks in sidebar, the web radio page is gone, no sound anymore. So, This does not become the reason to WONTFIX.

Alice: is "when I open Bookmarks in sidebar, the web radio page is gone, no sound anymore." a different bug perhaps? It seems like the minimum width point has been heard and resolved wontfix so nothing to track here for release.

(In reply to lsblakk@mozilla.com [:lsblakk] from comment #8) > Alice: is "when I open Bookmarks in sidebar, the web radio page is gone, no > sound anymore." a different bug perhaps? I mean your workaround is nothing to help. because sidebar is only one.