summaryrefslogtreecommitdiffstats
path: root/gfx
Commit message (Collapse)AuthorAgeLines
* [printing] Fix build bustage with --disable-printingMoonchild2020-05-23-0/+4
|
* Issue #80 - Include gfx/Logging.h in NativeFontResourceMac.cppadeshkp2020-05-20-0/+1
|
* Issue #80 - Include gfxEnv.h in gfx/gl/GLLibraryEGL.cppGaming4JC2020-05-20-0/+1
|
* Issue #80 - Fix up gfx/ipc and gfx/src for Linux.Moonchild2020-05-20-6/+1
| | | | This removes an unused Telemetry enum
* Issue #80- De-unify gfx/layersMoonchild2020-05-20-29/+61
| | | | | | | | Excludes layers/ipc/CompositorBridgeParent and CrossProcessCompositorBridgeParent because the latter purposely uses functions implemented in the former. See also code comment in CrossProcessCompositorBridgeParent.cpp Note: likely dead code for us anyway; likely not worth investing in to solve.
* Issue #80 - De-unify gfx/ycbcrMoonchild2020-05-20-1/+3
|
* Issue #80 - De-unify gfx/srcMoonchild2020-05-20-6/+4
|
* Issue #80 - De-unify gfx/skia and stop using dangerous optsMoonchild2020-05-20-12/+12
|
* Issue #80 - De-unify gfx/otsMoonchild2020-05-20-1/+1
|
* Issue #80 - De-unify gfx/ipcMoonchild2020-05-20-2/+23
|
* Issue #80 - De-unify gfx/harfbuzzMoonchild2020-05-20-11/+8
|
* Issue # 80 - Fix up gfx/2d/DataSurfaceHelpersMoonchild2020-05-20-7/+3
| | | | | De-unified build requires <string.h> instead of <cstring> to prevent stdlib confusion.
* Issue #80 - de-unify and fix up gfx/graphite2Moonchild2020-05-20-32/+28
| | | | | | | With de-unified building we have to re-apply the fix-up for <cstdio>, and additionally the same for <cstring> to prevent the compiler picking the wrong versions of standard functions.
* Issue #80 - Fix deps in gfxFont-Impl.hMoonchild2020-05-20-0/+3
|
* Issue #80 - Split out GetShapedWord template functionMoonchild2020-05-20-64/+84
|
* Issue #80 - Fix gfx/thebes Windows conditionalMoonchild2020-05-20-0/+2
|
* Issue #80 - De-unify gfx/glMoonchild2020-05-20-2/+21
|
* Issue #80 - De-unify gfx/configMoonchild2020-05-20-1/+1
|
* Issue #80 - De-unify gfx/cairoMoonchild2020-05-20-1/+1
|
* Issue #80 - De-unify gfx/2dMoonchild2020-05-20-10/+10
|
* Issue #80 - De-unify gfx/thebesMoonchild2020-05-20-22/+32
|
* Issue #457 - Silence some superfluous compiler warnings in cairoMoonchild2020-05-20-0/+5
|
* Issue #1450 - Remove NVidia 3D-Vision utilsMoonchild2020-05-06-308/+0
| | | | | | Legacy, unmaintained and untested D3D9 stereo output behind a hidden pref that nobody ever uses... :P 'nuf said. Resolves #1450
* [gfx] Put Skia-specific CTOR init behind Skia-conditional.wolfbeast2020-04-14-0/+2
|
* [Layers] Clear WrappingTextureSourceYCbCrBasic::mTexture correctlysotaro2020-04-14-0/+8
|
* Issue #1360 - Enable acceleration by default on all known-good platforms.wolfbeast2020-04-14-1/+5
|
* Issue #1360 - Part 1: Simplify layers acceleration prefs.wolfbeast2020-04-14-61/+7
| | | | | | | | | | | | | | | This gets rid of platform-dependent hard-coded defaults, but keeps build-time blocking if there is no GL provider (in which case layers acceleration almost certainly won't work because it needs a GL compositor and would likely crash without) New prefs are - layers.acceleration.enabled to enable HWA - layers.acceleration.force to force it enabled (requires .enabled to be set as well) This is the platform part of this issue. The rest will be front-end work (Preference UI integration and pref migration)
* Issue #1354 - Fix typowolfbeast2020-01-21-1/+1
|
* Issue #1354 - Clear the current context when MakeCurrent() fails.wolfbeast2020-01-20-95/+74
|
* Issue #1354 - Don't allow glsl[130,400] unless we have gpu_shader5wolfbeast2020-01-16-0/+19
| | | | | - Teach GLContext about gpu_shader5 - Downgrade shader language version if gpu_shader5 support isn't found.
* Issue #1354 - Cherry-pick ANGLE update for broken drivers that supportwolfbeast2020-01-16-23/+12
| | | | required indexing but not the extensions.
* Enable layers acceleration by default on GTK platforms.wolfbeast2019-12-20-5/+0
| | | | | | | "Why is this still `blocked by default for platform`.. Everyone on Linux forces it on anyway once they are aware of it." -- Tobin Tag #1319
* Issue #1288 - Part 5: Pass graphite fonts through OTS.wolfbeast2019-11-14-10/+1
| | | | | Since the updated OTS supports proper checking of graphite fonts we no longer need to rely of harfbuzz for them.
* Issue #1288 - Part 4: Update the OpenType Sanitizer component to 8.0.0wolfbeast2019-11-14-3290/+10961
|
* Issue #1274 - Part 5: Misc fixes and version update.wolfbeast2019-11-07-194/+25
|
* Issue #1274 - Part 4: Remove some unnecessary checks for old Windows versions.wolfbeast2019-11-07-28/+4
| | | | This gets rid of deprecated GetVersionEx() calls as a bonus.
* Issue #1274 - Part 3: Update libpixman licensingwolfbeast2019-11-07-0/+55
|
* Issue #1274 - Part 2: Update Windows prerequisite defines.wolfbeast2019-11-07-18/+24
|
* Issue #1274 - Part 1: Adopt the cairo version as our own.wolfbeast2019-11-07-31460/+650
| | | | | | | | | - Move header licensing from tri-license to MPL 2.0. MPL-compatible other licensing has been retained where originally present. - Remove individual superseded licensing terms. - Remove patches, outdated readmes & incomplete patch summaries. - Remove incomplete cairo release notes (only went up to 1.6.4 anyway). - Rewrite COPYING to indicate the current state of the library in tree.
* Correctly return zero vertices if clipping plane 0 or 2 clip away theMarkus Stange2019-09-04-15/+91
| | | | | | | | | | | | | | | | | | entire polygon. This fixes a bug that was introduced three years ago in BZ bug 1268854. What happened was that the final pass over the polygon assumed that the current polygon was living in plane[0]. But due to the double buffering, the "current" polygon alternates between plane[0] and plane[1]. The bug had also introduced an early exit so that we could hit the final pass at a time where the current, now empty, polygon was in plane[1]. So we would incorrectly treat all 32 points in plane[0] as part of the final polygon. This bug was responsible for intermittently unreasonable numbers in CompositorOGL's fill rate / overdraw overlay. This fixes a regression caused by the fix for CVE-2016-5252.
* Revert "Correctly return zero vertices if clipping plane 0 or 2 clip away the"wolfbeast2019-09-04-13/+11
| | | | This reverts commit 09a8b2f19689b679b1268a3004ec5e3f37b9732a.
* Correctly return zero vertices if clipping plane 0 or 2 clip away thewolfbeast2019-09-01-11/+13
| | | | | | entire polygon. This fixes a regression caused by the fix for CVE-2016-5252
* Issue #438: Add an IsRectilinear helper method to gfxMatrix.wolfbeast2019-08-14-0/+12
|
* Fix call to macro `MOZ_ASSERT_UNREACHABLE`adeshkp2019-07-23-1/+1
| | | Fallout from 227b23606b0401245c9f0b15effd45b876b90260
* Add CheckedInt check for GL texture uploads.wolfbeast2019-07-22-3/+37
|
* Make extra sure Compositables don't refer back to layers after reassignment.wolfbeast2019-05-28-5/+19
|
* Port an upstream Skia fix.wolfbeast2019-05-27-2/+3
|
* Issue #1101 - Support gzip-compressed SVGs in OpenType+SVG fontsGaming4JC2019-05-23-0/+38
|
* Enable double buffering when using XRENDER.Mihai Moldovan2019-05-22-1/+14
| | | | | | | | | This fixes flickering/bars/stripes showing up during quickly-updating operations on Intel hardware when using XRENDER. For more information, refer to the code comment. See #1061
* When using XRENDER, create Xlib-based offscreen image surfaces.Mihai Moldovan2019-04-27-8/+5
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | Mozilla tried to enable XRENDER support with backends other than Cairo in 286348:e13aaaaf1962 / https://hg.mozilla.org/mozilla-central/rev/e13aaaaf1962 - at least until they decided to completely remove XRENDER support. The change looked innocent enough, but actually turned out to do exactly the opposite: it forcefully enabled image offscreen surfaces with GTK2 when it was previously disabled (since gfxPrefs::UseImageOffscreenSurfaces() will always return true) and, by extension, disabled the XRENDER-based functionality by creating a non-Xlib surface. Interestingly, a previously enabled double buffering check was also disabled by this, but since the comment for this was diverging with the code, that behavior just sounds like yet another bug. Instead of disabling image offscreen surfaces (at least when using the GTK2 backend), let's force the creation of Xlib-based image surfaces when XRENDER support is enabled. This will let UXP use the more common/modern code paths, but also make scrolling much faster again. Too fast scrolling may induce tearing (if not smoothed), but on the other hand performs much better in remote computing contexts. As an added benefit, GTK3-based builds should roughly behave the same way. Further tests with the GTK3-backend enabled will be required in the future.
generated by cgit v1.2.3 (git 2.25.1) at 2024-11-26 06:52:45 +0000