Closed Bug 1209828 Opened 9 years ago Closed 9 years ago

about:config seems completely useless on samsung galaxy tab 2 7.0 in the 9/29 nightly the 9/28 nightly worked just fine

Categories

(Core :: Graphics: Layers, defect)

ARM
Android
defect
Not set
major

Tracking

()

RESOLVED DUPLICATE of bug 1209801
Tracking Status
firefox44 --- verified

People

(Reporter: wgianopoulos, Unassigned)

References

Details

(Keywords: regression)

Attachments

(2 files)

It is not at all clear how to do a search for an about:config key or to filter by them to get to the one you want to change.  I was asked by a developer to alter layers.tiles.adjust to false in about:config to debug a painting issue and I could not figure out how to do it.  I had to resort to installing the 9/28 nightly, changing the about:config parameter as requested and then updating the browser to give the requested information.
I don't see any new issue with about:config on today's nightly. Both my table and phone devices work as expected. 

Possibly related to your complaint...

I've notice that with recent changes to the front-end designed to make the UI appear responsive faster (before Gecko) at startup, we sometimes render pages before supporting scripts seem available to generate / respond to messages passed to core.

I see laggy response to expected behavior in about:config, and have noticed it also in text selection caret behaviour.

Can you describe the problem in more detail / screenshot / etc?
Huh?  The problem is tat you have removed the ability to filter as has always worked on desktop or search as has always worked on Android.  so that there is no way to find the preference you wish to change to be able to change it.  I have no idea what I would show a screenshot of.   the whole issue is the option does not exist so no way to show a screenshot of it.
Close your eyes and you will see a screenshot of nothing.
(In reply to Mark Capella [:capella] from comment #1)
> I don't see any new issue with about:config on today's nightly. Both my
> table and phone devices work as expected. 
> 
> Possibly related to your complaint...
> 
> I've notice that with recent changes to the front-end designed to make the
> UI appear responsive faster (before Gecko) at startup, we sometimes render
> pages before supporting scripts seem available to generate / respond to
> messages passed to core.
> 
> I see laggy response to expected behavior in about:config, and have noticed
> it also in text selection caret behaviour.
> 
> Can you describe the problem in more detail / screenshot / etc?

Well then please explain how this new interface works because the search has been removed.
IN fact since this kept me form answering a question a devloper asked for to work on an issue I ma raising the importance to blocker.
Severity: major → blocker
(In reply to Mark Capella [:capella] from comment #1)
> I don't see any new issue with about:config on today's nightly. Both my
> table and phone devices work as expected. 
> 
> Possibly related to your complaint...
> 
> I've notice that with recent changes to the front-end designed to make the
> UI appear responsive faster (before Gecko) at startup, we sometimes render
> pages before supporting scripts seem available to generate / respond to
> messages passed to core.
> 
> I see laggy response to expected behavior in about:config, and have noticed
> it also in text selection caret behaviour.
> 
> Can you describe the problem in more detail / screenshot / etc?

I do not understand your comment at all the entire about:config UI was changed between the 9/28 and 9/29 nighties if you see not difference you need new glasses.  It is not at all clear how to get to the preference you want to change in the new design making this a really bad UX change.  I really don't think the Firefox UX people are really skilled in UX.  Just my opinion I could be wrong.
OH and please note this is an Firefox for Android bug.  Perhaps you don't see the issue on desktop?
Attached image fennec-aboutconfig.png
I updated two devices to 9/29 Nightly and about:config still shows the search/filter UI.
Well then now i am confused.  I will post screen shots of what i get tomorrow.
OK it still shows a useful UI on my Nexus running lollipop  hmm let me see if the workaround for the other bug fixes it on my samsung.
OK this seems to be only an issue on my Samsung Galaxy Tab 2 7.0 running Android 4.2.2 and not on my nexus running Lollipop, but it is still a regression between 9/28 and 9/29 and not fixed by setting layers.tiles.adjust = false.
Summary: about:config seems completely useless in the 9/29 nightly the 9/28 hightly worked just fine → about:config seems completely useless on samngsum galaxy tab 2 7.0 in the 9/29 nightly the 9/28 hightly worked just fine
Summary: about:config seems completely useless on samngsum galaxy tab 2 7.0 in the 9/29 nightly the 9/28 hightly worked just fine → about:config seems completely useless on samsung galaxy tab 2 7.0 in the 9/29 nightly the 9/28 nightly worked just fine
For clarity, regarding the |layers.tiles.adjust = false| matter, iirc with you and snorp this is a proposed solution to a different issue (correct?)

In regard to the Tab 2, can you observe anything in logcat? That screen shot you promised might show me something. I knew of no planned Android changes in this area, and saw no signs of recent code mods so I'm confused a bit also :)
I suspect it is caused by the same checkin and the issue is that it is dependent on some interface that is not present in android 4.2.2.  i am bisecting both issues now.  but is suspect it will sow up as the same checkin caused both issues.  However, it is very late here so probably no results until tomorrow.
Severity: blocker → major
Blocks: 1182665
Keywords: regression
Hg bisect said:

The first bad revision is:
changeset:   264757:9fea88097171
user:        James Willcox <snorp@snorp.net>
date:        Wed Aug 26 17:33:16 2015 -0500
summary:     Bug 1182665 - Adjust tile sizes depending on the screen size r=nical
Status: NEW → RESOLVED
Closed: 9 years ago
Resolution: --- → DUPLICATE
Status: RESOLVED → REOPENED
Resolution: DUPLICATE → ---
It seems I was wrong.  The workaround I had thought fixed both bugs (setting the texture size to 256x256) actually did not fix this one.
Status: REOPENED → NEW
I re-bisected this and came up with this:

The first bad revision is:
changeset:   264758:1c5c67287ea8
user:        James Willcox <snorp@snorp.net>
date:        Thu Sep 03 11:43:09 2015 -0500
summary:     Bug 1201541 - Use SingleTiledContentClient for non-scrollable layers on Android r=mattwoodrow
Blocks: 1201541
No longer blocks: 1182665
Component: General → Graphics: Layers
Product: Firefox for Android → Core
I have verified that setting layers.single-tile.enabled to false avoids the issue.
OS: Unspecified → Android
Hardware: Unspecified → ARM
Perhaps we should just set layers.single-tile.enabled to false for blocklisted devices.
Snorp, can you take a look at this?
Flags: needinfo?(snorp)
I believe this is a dup of bug 1209801 which is now fixed.
Status: NEW → RESOLVED
Closed: 9 years ago9 years ago
Resolution: --- → DUPLICATE
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: