Closed
Bug 1089838
Opened 10 years ago
Closed 3 years ago
'Request desktop site' is confusing
Categories
(Firefox for Android Graveyard :: General, defect)
Tracking
(fennec+)
RESOLVED
INCOMPLETE
Tracking | Status | |
---|---|---|
fennec | + | --- |
People
(Reporter: miketaylr, Unassigned)
Details
Attachments
(1 file)
7.17 KB,
patch
|
Margaret
:
review+
|
Details | Diff | Splinter Review |
It shouldn't be possible to "Request Desktop Site" from "about:home" and similar non-webby URLs. I see that Bug 711595 fixed this a while ago, but it seems to have regressed at some point.
Reporter | ||
Updated•10 years ago
|
Assignee: nobody → miket
Status: NEW → ASSIGNED
OS: Mac OS X → Android
Hardware: x86 → All
Reporter | ||
Comment 1•10 years ago
|
||
Simple fix + a robocop test to make sure this doesn't regress in the future. Margaret, r? because you fixed this once before. :)
Reporter | ||
Comment 2•10 years ago
|
||
Just to note:
> desktopMode.setEnabled(StringUtils.isShareableUrl(tab.getURL()));
It feels a little funny to use "isShareableUrl" as a test for webfacing-ness. It's got the right semantics though. Dunno if we should rename that to something more generic (no idea what that would be) and update other code that uses isShareableUrl.
Comment 3•10 years ago
|
||
Comment on attachment 8512224 [details] [diff] [review] 1089838.patch Review of attachment 8512224 [details] [diff] [review]: ----------------------------------------------------------------- Good catch! Sucks that regressed :/ Thanks for making a test. ::: mobile/android/base/BrowserApp.java @@ +2605,5 @@ > bookmark.setIcon(tab.isBookmark() ? R.drawable.ic_menu_bookmark_remove : R.drawable.ic_menu_bookmark_add); > > back.setEnabled(tab.canDoBack()); > forward.setEnabled(tab.canDoForward()); > + // Enable desktop mode menuitem only for web-facing URLs Nit: Add an empty line above this comment line. ::: mobile/android/base/tests/components/AppMenuComponent.java @@ +104,5 @@ > + public void assertMenuItemIsEnabledAndVisible(MenuItem menuItem) { > + openAppMenu(); > + > + final View menuItemView = findAppMenuItemView(menuItem.getString(mSolo)); > + fAssertTrue("The page menu item is enabled", menuItemView.isEnabled()); Update these comments to be more generic, since these methods aren't specifically testing the page menu item.
Attachment #8512224 -
Flags: review?(margaret.leibovic) → review+
Comment 4•10 years ago
|
||
Hm, I thought this came up before and we decided that RDS should still be enabled since RDS is a per-tab setting, not per-site setting. That is, I might want to switch RDS on before going to a site.
Comment 5•10 years ago
|
||
(In reply to Brian Nicholson (:bnicholson) from comment #4) > Hm, I thought this came up before and we decided that RDS should still be > enabled since RDS is a per-tab setting, not per-site setting. That is, I > might want to switch RDS on before going to a site. Oh, yeah, better memory than me. We should try to dig up the bug where we actually removed this.
Comment 6•10 years ago
|
||
(In reply to Mike Taylor [:miketaylr] from comment #2) > Just to note: > > > desktopMode.setEnabled(StringUtils.isShareableUrl(tab.getURL())); > > It feels a little funny to use "isShareableUrl" as a test for > webfacing-ness. It's got the right semantics though. Dunno if we should > rename that to something more generic (no idea what that would be) and > update other code that uses isShareableUrl. We do have AboutPages.isAboutPage for this kind of thing.
Reporter | ||
Comment 7•10 years ago
|
||
(In reply to Richard Newman [:rnewman] from comment #6) > We do have AboutPages.isAboutPage for this kind of thing. That's cool. But doesn't cover chrome:// file:// and resource://.(In reply to :Margaret Leibovic from comment #5) > (In reply to Brian Nicholson (:bnicholson) from comment #4) > > Hm, I thought this came up before and we decided that RDS should still be > > enabled since RDS is a per-tab setting, not per-site setting. That is, I > > might want to switch RDS on before going to a site. > > Oh, yeah, better memory than me. We should try to dig up the bug where we > actually removed this. Seems like a good topic for the mailing list. I'll start a thread tomorrow morning (My feelings won't be hurt either way--I noticed this because right now requesting desktop content prompts the user to report a site issue. Obviously that makes no sense for about:home et al.)
Reporter | ||
Comment 8•10 years ago
|
||
Eh, actually I don't know if you guys hash out stuff like this on the mailing list--or if discussion is better here in bugs.
Reporter | ||
Comment 9•10 years ago
|
||
It looks like the discussion happened in https://bugzilla.mozilla.org/show_bug.cgi?id=790954#c15 and https://bugzilla.mozilla.org/show_bug.cgi?id=790954#c16. I get the reasoning, so this wasn't really a regression. Since https://bugzilla.mozilla.org/show_bug.cgi?id=767795 was WONTFIX'd, I'll go ahead and WONTFIX this one myself. Should have done some better searching, sorry!
Status: ASSIGNED → RESOLVED
Closed: 10 years ago
Resolution: --- → WONTFIX
Updated•10 years ago
|
tracking-fennec: --- → ?
Comment 10•10 years ago
|
||
It doesn't make sense to me to "request desktop site" for a protocol where we don't send a request. That includes about:, chrome: and file:. The behavior might be per-tab, but the user is taking the action in the context of a tab.
Status: RESOLVED → REOPENED
Resolution: WONTFIX → ---
Comment 11•10 years ago
|
||
(In reply to Brad Lassey [:blassey] (use needinfo?) from comment #10) > The behavior might be per-tab, but the user is taking the action in the > context of a tab. What does "context of a tab" mean? Is that not "per-tab"?
Comment 12•10 years ago
|
||
I would suggest a tiny rewording: "Request desktop site" -> "Request desktop sites".
Comment 13•10 years ago
|
||
A request was made to look at for a better wording for this menu.
Updated•10 years ago
|
tracking-fennec: ? → +
Summary: Disable desktopMode for non-webfacing content → 'Request desktop site' is confusing
Assignee: miket → nobody
Comment 14•3 years ago
|
||
We have completed our launch of our new Firefox on Android. The development of the new versions use GitHub for issue tracking. If the bug report still reproduces in a current version of [Firefox on Android nightly](https://play.google.com/store/apps/details?id=org.mozilla.fenix) an issue can be reported at the [Fenix GitHub project](https://github.com/mozilla-mobile/fenix/). If you want to discuss your report please use [Mozilla's chat](https://wiki.mozilla.org/Matrix#Connect_to_Matrix) server https://chat.mozilla.org and join the [#fenix](https://chat.mozilla.org/#/room/#fenix:mozilla.org) channel.
Status: REOPENED → RESOLVED
Closed: 10 years ago → 3 years ago
Resolution: --- → INCOMPLETE
Assignee | ||
Updated•3 years ago
|
Product: Firefox for Android → Firefox for Android Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•