Merge mozilla master, add docker-compose.yml and update README #6
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Remove duplicated --toolbar-height definition in the css
…to font size (bug 1917734)
Correctly compute the font size when printing a text field with an auto font size (bug 1917734)
Increase the size of the toolbar depending on the uidensity (bug 1171799)
Add Calixte to the list of authors
…tton Remove the unused `splitToolbarButton` CSS class (PR 18385 follow-up)
…ainer Unify separate `#toolbarContainer`-blocks in the CSS (PR 18385 follow-up)
…ent` Given that the `WorkerTransport`-constructor will access all possible factory-instances, let's ensure that the `transportFactory`-object always has a consistent shape regardless of other options. Also, since `useWorkerFetch` is always true in MOZCENTRAL builds we never need to create `CMapReaderFactory`/`StandardFontDataFactory`-instances there.
… tile dimensions (bug 1837738) It fixes mozilla#16038. The idea is to create a pattern having the steps for dimensions and then draw the base tile and the different overlapping parts on it.
Fix the rendering of tiling pattern when the steps are lower than the tile dimensions (bug 1837738)
…init Slightly re-factor the `transportFactory` initialization in `getDocument`
…ls (PR 15281 follow-up) This became unused in PR 15281, however that patch clearly missed some occurrences; sorry about that!
…-trackTransform Remove `trackTransform` arguments from `CachedCanvases.getCanvas`-calls (PR 15281 follow-up)
Given the following excerpt from the [Wikipedia article](https://en.wikipedia.org/wiki/Gill_Sans), mapping this to Helvetica should hopefully be fine: > It has been described as "the British Helvetica" because of its lasting popularity in British design.
Add basic support for non-embedded GillSansMT fonts (issue 18801)
…ndary toolbar (bug 1911980)
[Editor] When deleting an annotation with popup, then delete the popup too
[Editor] Avoid to have a selected stamp annotation on top of the secondary toolbar (bug 1911980)
…(PR 15522 follow-up) We disable any non-default CursorTool in PresentationMode and during Editing, since they don't make sense there and to prevent problems such as e.g. [bug 1792422](https://bugzilla.mozilla.org/show_bug.cgi?id=1792422). Hence it seems like a good idea to *also* disable the relevant SecondaryToolbar-buttons, to avoid the user being surprised that the CursorTools-buttons do nothing if clicked.
Ensure that the CursorTools-buttons are disabled e.g. during editing (PR 15522 follow-up)
This patch updates the minimum supported browsers as follows: - Google Chrome 103[1], which was released on 2022-06-21; see https://chromereleases.googleblog.com/2022/06/stable-channel-update-for-desktop_21.html Note that nowadays we usually try, where feasible and possible, to support browsers that are about two years old. By limiting support to only "recent" browsers we reduce the risk of holding back improvements of the *built-in* Firefox PDF Viewer, and also (significantly) reduce the maintenance/support burden for the PDF.js contributors. *Please note:* As always, the minimum supported browser version assumes that a `legacy`-build of the PDF.js library is being used; see https://github.com/mozilla/pdf.js/wiki/Frequently-Asked-Questions#faq-support --- [1] This is consistent with the minimum supported version in the recently updated Google Chrome addon.
[api-minor] Update the minimum supported Google Chrome version to 103
…"optionalcontentconfigchanged" events The current implementation won't work correctly in some cases, e.g. if RBGroups are present, which means that it's possible for the UI to get out-of-sync with the actual optionalContent-state. To avoid querying the DOM unnecessarily we cache the last known UI-state and compare with the actual optionalContent-state, which thus replaces the previously used hash-comparison.
…date-UI Re-factor how `PDFLayerViewer` decides if the UI needs to updated on "optionalcontentconfigchanged" events
This reverts commit 4c1fbed.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
How? (Comments on implementation)
dockerfileanddocker-compose.ymlto use pdfjs locally in docker.README: how to launch pdfjs in docker locally.