1120251 - The context menu is no longer accessible on Android after switching to Tablet UI on a phone

Status: RESOLVED WONTFIX

(Firefox for Android Graveyard :: General, defect)

Description

[Achwaq Khalid]

User Agent: Mozilla/5.0 (Windows NT 6.3; WOW64; rv:37.0) Gecko/20100101 Firefox/37.0
Build ID: 20150111030201

Steps to reproduce:

In order to get the tablet UI on a Galaxy Note 3 running Android 5 i changed the default lcd density from 480 down to 240 in build.prop


Actual results:

after rebooting the device

1 - run firefox
2 -  left click =====> the contextual menu doesn't appear


Expected results:

should show the contextual menu after clicking on the physical left button or provide a clickable button at the top right corner just like in the default Android browser

Comment 1

[Achwaq Khalid]

WONTFIX!!! dare to explain why

Comment 2

[Mark Finkle (:mfinkle) (use needinfo?)]

(In reply to Achwaq Khalid from comment #0)

> Steps to reproduce:
> 
> In order to get the tablet UI on a Galaxy Note 3 running Android 5 i changed
> the default lcd density from 480 down to 240 in build.prop

We do not support this type of setup.

Comment 3

[Achwaq Khalid]

Attachment: Screenshot (Jan 12, 2015 4_43_20 PM).png

Comment 4

[Achwaq Khalid]

(In reply to Mark Finkle (:mfinkle) from comment #2)
> (In reply to Achwaq Khalid from comment #0)
> 
> > Steps to reproduce:
> > 
> > In order to get the tablet UI on a Galaxy Note 3 running Android 5 i changed
> > the default lcd density from 480 down to 240 in build.prop
> 
> We do not support this type of setup.

"We" talk as a Mozilla representative or is it just "You and Aaron" because at Chrome "They" do actually provide native support for all of "Us = http://forum.xda-developers.com/showthread.php?t=2487523"

See screenshot

Comment 5

[Achwaq Khalid]

"this type of setup" is just the low level way to get this work done, otherwise you can always do it in Setting>Display>Display Density

Comment 6

[Richard Newman [:rnewman]]

(In reply to Achwaq Khalid from comment #4)

> "We" talk as a Mozilla representative or is it just "You and Aaron"

Mark owns Firefox for Android.


> See screenshot

If you can change display density on a stock Note, without installing a custom ROM, then we can have a conversation about whether we should support that.

If you need to root your device to get to this point, which is the impression I'm getting from that xda-dev thread, then you're on your own.

Comment 7

[Achwaq Khalid]

(In reply to Richard Newman [:rnewman] from comment #6)

> Mark owns Firefox for Android.

whuuuuuuut! i seriously don't know how to respond to that!!!!
 
> If you can change display density on a stock Note, without installing a
> custom ROM, then we can have a conversation about whether we should support
> that.

Alright Mr. Ricahrd I own another OnePlus One which comes Pre-Rooted with a custom Cyanogenmod ROM, how do i proceed now?

Comment 8

[Aaron Train [:aaronmt]]

By marking this bug invalid it rejects the validity of the report. It is a bug, but the drivers of the project have decided not to fix it. The environment is not something we support nor do we wish to chase after other similar bugs un unsupported environments. Please do not alter this bug's status.

Comment 9

[Richard Newman [:rnewman]]

(In reply to Achwaq Khalid from comment #7)
> (In reply to Richard Newman [:rnewman] from comment #6)
> 
> > Mark owns Firefox for Android.
> 
> whuuuuuuut! i seriously don't know how to respond to that!!!!

You might want to briefly read https://wiki.mozilla.org/Modules to understand how the Mozilla project works.

In particular, Firefox for Android is here:

https://wiki.mozilla.org/Modules/Other#Fennec


> Alright Mr. Ricahrd I own another OnePlus One which comes Pre-Rooted with a
> custom Cyanogenmod ROM, how do i proceed now?

Does it allow you to change display density in its stock configuration?

As I said: if you have a stock device that allows you to make changes that cause bugs in Firefox, then we can assess whether there are enough impacted users to make it worth addressing (same as with any bug).

Issues that arise from jumping through hoops that might be expected to break an app -- like rooting and having the OS give conflicting information about its screen configuration -- typically end up being WONTFIXed.

It's like going to the doctor and telling him "it hurts when I poke myself in the eye": his recommendation is "don't do that".

Comment 10

[Achwaq Khalid]

(In reply to Richard Newman [:rnewman] from comment #9)

Your assertion though! And you think i will listen to that doctor, thank God another (We won't call him experienced just for respect to Mozilla) more adventurous doctor is here to deal with the task (hum hum chrome :P )

Regards.

Comment 11

[Michael Comella (:mcomella) [NI reported issues only: ex-Mozilla]]

Because I didn't feel the answers in this bug would have been fully satisfying to me, I just wanted to elaborate a bit.

Unfortunately, there are only so many developers working on the project so we have to prioritize bug fixes (and feature implementations) by the number of users they affect. So as per Richard's comment,

(In reply to Richard Newman [:rnewman] from comment #9)
> As I said: if you have a stock device that allows you to make changes that
> cause bugs in Firefox, then we can assess whether there are enough impacted
> users to make it worth addressing (same as with any bug).

The majority of users use stock devices that they haven't tinkered with and thus we prioritize issues for these users.

Since this issue isn't trivial to fix (note: there even exists some precedent, e.g. bug 1022668), we just don't have the cycles to spare for it. However, that wouldn't stop a new contributor from coming along and fixing this issue.