Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add comment for blank pages on Android #136

Closed
wants to merge 2 commits into from
Closed

Add comment for blank pages on Android #136

wants to merge 2 commits into from

Conversation

licaon-kter
Copy link

No description provided.

@pyllyukko
Copy link
Owner

What does this mean exactly? I don't get it.

@licaon-kter
Copy link
Author

Which part, my comment or what the issue is with that config as true?

@pyllyukko
Copy link
Owner

What the issue is.

@licaon-kter
Copy link
Author

I agree, ok, maybe rephrase it as might then?

Regarding canvas, won't it be better to recommend https://github.com/kkapsner/CanvasBlocker instead?

@pyllyukko
Copy link
Owner

We already recommend Canvasblocker + AntiCanvas addon (see readme).

Well I wouldn't say we recommend those. They are just on the TODO list. If we're gonna talk about canvas stuff, I'd suggest we'd move to #38.

@pyllyukko
Copy link
Owner

Please close.

I still want to know what's this about. How are pages blank? Is it unusable? @licaon-kter: Can you provide some screenshots or some more detail?

@licaon-kter
Copy link
Author

Oh, I missed the recommendation, indeed you do.

Now, regarding this PR, I forgot to add the screenshots:

@licaon-kter
Copy link
Author

Sony Xperia 5.1.1
Firefox 45.0.1 (stable) or Orfox 38

What do you mean by platform?

On Android, at least on my device, you can set it up only via about:config, although once you've disabled it (as you do now), you can't see any pages, not even internal ones, hence you need to either edit prefs.js (if you have root) or clear all app data.

@licaon-kter
Copy link
Author

Z3. Then it might be a ROM thing, so this PR might help someone (besides me).

@pyllyukko
Copy link
Owner

Ok. Now I'm starting to understand :)

Maybe it would still be better to have this on the known problems part of the README instead?

@licaon-kter
Copy link
Author

Yeah maybe, afaik, no one reads anything :), let alone the source, README might be easier for the search engines to grok and help someone somewhere.

@pyllyukko
Copy link
Owner

I added a note to the README. @licaon-kter: Do you think this is sufficient?

And thanks for reporting this problem.

@licaon-kter
Copy link
Author

Yes, I was just writing kinda exactly the same text. Thanks :)

@licaon-kter
Copy link
Author

It's not limited to GitHub, it was just a sample c'mon, any page (both web and internal like Addons) will be blank, not slow, not with aliased fonts, not with missing UTF-8 coding, just plain blank, and you can't access about:config to change anything back... since it's blank.

I've searched before posting this and I did not find any reference regarding Android, just for desktop, and the problem was the other way around, acceleration ON was troublesome.

I don't see why some piece of info could be harmful here in any way, it would have helped me so I did not end up deleting 3 profiles and going all divide et impera on both user.js and prefs.js settings.

If this information is wrong, (it's a connection issue ONLY with it set up as true, really?) please direct me on what to test next, I'm interested in the true culprit.

@licaon-kter
Copy link
Author

I can't just install AOSP/CM13/etc, I can't unlock the bootloader, so it will be rejected as ROM specific, which is perfectly fine, plenty of Android versions go around being slightly broken in different ways.

Regarding a Firefox specific bug, I guess: https://bugzilla.mozilla.org/show_bug.cgi?id=1146783

@nodiscc
Copy link
Contributor

nodiscc commented Apr 9, 2016

related to Browser or the OS itself

Yes, so let's keep it in the doc (I have $random problem -> Your android ROM is broken and we can't fix it)

may scare people away because they see the 'mass' on problems

It's technical doc and I think it should reference all annoying problems (someone bothered to open an issue here) - even better, it has a one-line workaround.

@licaon-kter
Copy link
Author

We can't add for each 'problem' someone may have workaround's

Yes you can, that's the whole point of FAQs and Known issues sections since like forever.

You could just try to use chromium it uses similar rendering technique on android

And disable acceleration there too or what? You did understand that it works fine OOTB, unless I purposely/manually disable acceleration, right?

if you just could try the Beta FF version

I'll try it and come back here to signal a change or not.

I highly suggest to open an ticket yourself and report instead of link to something which is may another story.

Yes, it sounds the same, it might not be. I'll see to that too, yet another account meh, getting used to GitHub and its hosted projects, one account for them all :P

It worked for me

You do realize that does not mean anything. Hopefully you don't have any issue on your hardware, it would be pretty sad to hear that line from anyone else.

@takiainen
Copy link

I have this same issue, and definetly think it should be mentioned in readme. I've been trying to figure out during last few days which one of these hundred or so settings breaks my browser, until I found this.

I've got Oneplus One running darkobas MM ROM. I've tried 38 based Icecat mobile browser and latest Firefox from fdroid - both have same issue.

Everything is just blank, can't access about:config either.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants