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

Bug 639134 - update check for document colors #5511

Merged
merged 1 commit into from
Jan 22, 2015

Conversation

gijsk
Copy link
Contributor

@gijsk gijsk commented Nov 26, 2014

This checks for both prefs on the understanding that we need to work on older versions of Firefox. If that isn't the case, the first part of the if isn't necessary. This should only land if bug 639134 is resolved - I'd make the patch part of that bug, but AIUI pdfjs's canonical repo is on github, so...

This checks for both prefs on the understanding that we need to work on older versions of Firefox. If that isn't the case, the first part of the if isn't necessary. This should only land if bug 639134 is resolved - I'd make the patch part of that bug, but AIUI pdfjs's canonical repo is on github, so...
@yurydelendik
Copy link
Contributor

/botio-windows preview

@pdfjsbot
Copy link

pdfjsbot commented Dec 5, 2014

From: Bot.io (Windows)


Received

Command cmd_preview from @yurydelendik received. Current queue size: 0

Live output at: http://107.22.172.223:8877/ffe9923db37a0d1/output.txt

@yurydelendik yurydelendik self-assigned this Dec 5, 2014
@yurydelendik
Copy link
Contributor

https://bugzilla.mozilla.org/show_bug.cgi?id=639134 is landed in FF37 and patch looks good -- trying to figure out when we regressed the warning bar

@Snuffleupagus
Copy link
Collaborator

We might want to hold off with this PR, since there's apparently questions regarding the new pref, see https://groups.google.com/forum/#!topic/mozilla.dev.platform/th7gTtRSgo0.

@Snuffleupagus
Copy link
Collaborator

trying to figure out when we regressed the warning bar

When I'm looking at the code that should trigger the warning, viewer.js#L1741-L1749, I'm not sure how it ever worked :-)
The current code assumes that when the page has been rendered, so has the text layer. This is obviously not true in general, so we might need to add a textlayerrendered event as well (beside the pagerendered one).

@Snuffleupagus
Copy link
Collaborator

Do we need to wait for the resolution of https://bugzilla.mozilla.org/show_bug.cgi?id=1118032, or can we land this now? Also, should we use preprocessor tags? E.g.

  if (getIntPref('browser.display.document_color_use', 0) === 2) {
    return false;
  }
//#if !MOZCENTRAL
  if (!getBoolPref('browser.display.use_document_colors', true)) {
    return false;
  }
//#endif
  return true;

@gijsk
Copy link
Contributor Author

gijsk commented Jan 6, 2015

We don't need to wait; that bug will only change the representation of the pref in the preference pages, not the values of the pref

Snuffleupagus added a commit that referenced this pull request Jan 22, 2015
Bug 639134 - update check for document colors
@Snuffleupagus Snuffleupagus merged commit 8389f1d into mozilla:master Jan 22, 2015
@Snuffleupagus
Copy link
Collaborator

Thanks for the patch!

speedplane pushed a commit to speedplane/pdf.js that referenced this pull request Feb 24, 2015
Bug 639134 - update check for document colors
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