🧐 Breaking changes for fabric 6.0

[asturur]

b.0.0-beta16

This list is in progress and is meant to be an easy go to place to add things and find them when the time comes to write a document on what has changed. This will be a list of descriptive items, extended as needed to capture behavior changes. Apart from what is described here MANY bugs have been fixed in the process.

Generic concepts

• Imports we moved from import { fabric } from 'fabric' to import { Canvas, Rect, util } from 'fabric' or import * as fabric from 'fabric'. To avoid packaging issues node has its own entrypoint import { StaticCanvas } from 'fabric/node'. This means there is no fabric namespace/object anymore.

  • Introduced classRegistry to bridge the absence of a namespace
  • Introduced the env concept, getEnv to allow node/browser specific values/logic. That has made importing fabric in SSR possible and will allow offscreen support in the future.
  • renamed the following #9172:
  • fabric.Object => FabricObject
  • fabric.Text => FabricText
  • fabric.Image => FabricImage
  • Node's registerFont has been removed, use registerFont exposed by node canvas

• method chaining is now deprecated, don't use it anymore. Not all methods were chainable, and chaining seems to offer limited advantages ( maybe saving 1-2 bytes in the code you write when minified? unsure what else ). Just for consistency sake and to be free to start returning useful information from some methods we will stop using it. We didn't remove it from everywhere so that there isn't unnecessary breakage, but you should consider that unsafe to use, since will break entirely on the next major release after 6.0 ( add detailed list of where has been removed so far )

• Callbacks are mostly gone, all of the functions that took a callback now return a Promise, this on top of being breaking slightly alter code behavior when is fixed. Before sync code would execute the callback synchronously, now is chained to however the browser handle the promise ( not sure if it goes in the event loop and under which circumstances ). https://github.com/fabricjs/fabric.js/issues/3684

• TS: The code base is typed! If you used @types/fabric you should uninstall it

• Prototype Mutation: Fabric has moved to native classes. No more createClass or object.util.extend. You can still mutate the prototype, however, properties do not exist on the prototype in native classes. Look into getDefaults instead.

• scene vs. viewport We introduced these concepts to describe the rendering/view planes as follows: The viewer is viewing the scene (what is rendered/"playing") from the viewport. The scene was considered is the past as the absolute plane whereas the viewport wasn't #9175. Normally geometry calculations occur in the scene with the exception of padding which is a viewport scalar.

  • All events have a scenePoint and viewportPoint properties replacing the deprecated and confusing absolutePointer and pointer properties. Brushes are still in need of this change.
  • dep Canvas#getPointer in favor of getScenePoint or getViewportPoint
  • Using viewportTransform is rather confusing with this change (especially with sendPointToPlane etc.) perhaps be renaming to sceneTransform is the correct migration path in the future.

• React Compatibility:

  • Ensure proper disposal in useEffect, especially with React 18. Refer to this hook for guidance.
  • Async Disposal: Handle async nature of dispose method. The asynchronous disposal of Canvas and StaticCanvas safeguards an edge case in which dispose is called while rendering is still in progress. This should burden your react app.
  • DOM Mutation: Fabric modifies the DOM and cleans up after itself as long as Canvas#dispose is called

Collection

• not available as a standard object as fabric.Collection any longer, was never meant to, it was a constrain of the previous build system ( we had no imports or require or bundling before ).
• insertAt method signature changed from insertAt(object, index) to insertAt(index, ...objects)
• Collection now owns the stack too, methods were renamed to accommodate Group:
  • sendObjectToBack sendToBack
  • bringObjectToFront bringToFront
  • sendObjectBackwards sendBackwards
  • bringObjectForward bringForward
  • moveObjectTo moveTo
• Support to stack operations with active selection is gone

Canvas and StaticCanvas

• Canvas.dispose and StaticCanvas.dispose are now async In order to handle some concurrency issue with requestAnimationFrame, dispose is now checking and waiting for any uncancellable render to finish. This could have some side effects, especially in complex environments with UI frameworks and hot reload of code.

• trying to initialize a canvas that has already been initialized #7776 is not breaking, it saves the dev from a silent breakage that they weren't aware of

• removed canvas.straightenObject wasn't really useful.

• changed cloneWithoutData , now it does not clone backgrounds.

• canvas.clone now correctly return either a canvas or staticCanvas

• drawClipPathOnCanvas signature changed: now accepts the clipPath as a second argument instead of rechecking its existence

• getCenter renamed to getCenterPoint #7699

• add returns the length of the array of objects after adding, like Array#push

• remove returns an array with the removed objects inside

• insertAt method signature changed (refer to the Collection section)

• removed sendToBack, bringToFront, sendBackward, moveTo, bringForward ( and gained similar methods from collection (refer to the Collection section)

• Canvas#freeDrawingBrush is not set by default

• scene vs. viewport changes

  • dep getPointer in favor of getScenePoint or getViewportPoint
  • rm _normalizePointer, restorePointerVpt

• rm interactive flag, use instance of Canvas instead

• rm setBackgroundColor, setBackgroundImage, setOverlayColor, setOverlayImage: assign the property directly and render the canvas

Object

• BREAKING Coords system improvements:
  • removed lineCoords
  • aCoords should be treated as protected , if you need the scene corners of an object use getCoords
  • fixed coords to respect grouping and nesting, see the Group section
  • removed absolute, calculate from geometry methods signatures (all listed methods operate in the scene):
    • getCoords
    • intersectsWithRect
    • intersectsWithObject
    • isContainedWithinObject
    • isContainedWithinRect
    • getBoundingRect
    • containsPoint changed signature entirely and fixed
  • getRelativeXY/setRelativeXY to get/set the coordinate in the parent plane, getXY/setXY to get/set the coordinate in the scene plane
  • adjustPosition is gone. It took a parameter only, was internally unused, didn't take care of internal edge cases setPositionByOrigin is more flexible
  • rm _setOriginToCenter and _resetOrigin #9179
  • Control coords (oCoords) are calculated only if the object has a canvas ref
• type has become a static field and should be used only for serialization with classRegistry. There is still a deprecated getter on the object for compatibility reasons. Avoid using it.
• Object looses the stack methods, instead of guessing which was the stack we refer to when we move forward/backward we do that from the stack itself #8461, see the Collection section
• stateful functionality is deprecated, is officially removed, but is still reacheable. Don't use it. Comparing large set of propeties to detect a change doesn't really play well neither with performance nor with edge cases. stateful and statefulCache are removed. stateful was used to fire an object modified every render cycle in which a change in state properties was determiend. All the events that can modify an object already fire an object:modified event, and the user has no ability to change colors or state outside developer written code, so there is no really need for event firing here. statefulCache was an experiment and the suggestion to use set(property, value) replaced it since long. FabricJS internally still use some stateful logic for now, but the intention is to get rid of it.
• methods like center, centerH, centerV, viewportCenter are gone. Those were aliases for the canvas methods, use them instead.
• animate changed to adapt to animation changes
• The controls object is not shared between instances - it is not on the prototype as all class fields
• BREAKING: Object#getObjectScaling, Object#getTotalObjectScaling now returns Point instead of {scaleX,scaleY} #7710

Text

• see Text styles under the Serialization section
• rename data-fabric-hiddentextarea to data-fabric with value textarea, if you were using hasAttribute('data-fabric-hiddentextarea') now you have to use getAttribute('data-fabric') and then check for equality with textarea or change your cssSelector accordingly.
• _getStyleDeclaration returns an empty object instead of undefined when style is not set.
• controls can be used in editing mode

Polyline Polygon Path

• _setPositionDimensions (considered private in the past), has been renamed to setDimensions. The logic with which Polyline based object calculate the size is changed. There wasn't an api in 5.x to change the size, but devs needed to do it anyway and the alternative was to create a new object. Is not called setPositionAndDimensions because the logic to correcly change size while keeping a visual correct position is not there yet and maybe it won't.
• exposed long desired poly controls createPolyControls

Group

• complete rewrite described in #7670
• CONCEPT: Group rewrite exposes a change in concept - strict object tree. An object can belong to one parent.
• exposed the parent property on FabricObject alongside group to allow an object to return to its parent after being deselected from an active selection.
• addWithUpdate is gone, now add does what it has to do.
• LayoutManager has been introduced to handle group layout #9152. By default it will be fit-content, meaning the group will fit around its objects, updating when objects are added/removed/modified.

Controls

• expose shouldActivate for ease of use #8934 #9374
• no longer shared, they are a class field

Serialization

• Text#styles is now exported differently. This is BREAKING only if you are handling the style object post export The default object we exported was large most of the time, with tons of empty keys and verbosity. It seems reasonable to think that most of the time text is styled in some chunk of text with coherent different styles ( eg: a red word in a black text or some words underlined and some not more than a rainbow of different stylings per object ) for that reason we changed the approach of serialization to an array with start and end index for the style. We didn't apply that to actual runtime code because we were unsure of performance, so at least for version 6, styles at runtime are going to be the same. It is highly recommended to not fiddle with the style object directly and to treat it as internal, using the public facing methods to apply changes. https://github.com/fabricjs/fabric.js/pull/8006
• populateWithProperties => pick populate with properties was used internally to add the extra options to exported objects. Between spread operator and new syntax, a generic pick approach seemed more correct.
• toJSON is not an alias of toObject. This was a long standing bug, but also a breaking change. toJSON never accepted additional properties and will give you only the default object export. toJSON is meant for JSON#stringify interoperability and is not meant to be used in your code base directly. reference #8111
• classRegistry => register your subclasses to use them during serialization
• NUM_FRACTION_DIGIT moved to config and incremented from 2 to 4

Brushes

PatternBrush: removed the getPatternSrcFunction. Wasn't working anymore since the refactor of Pattern and also a super weird practice.

Animation

• animation util does not accept anymore the += or -= syntax for changes, nor accept the byValue option. You can specify an animation only by startValue and endValue.
• Every animation returns a class with a cancel method to cancel the animation.
• Animation callback onChange and onComplete will fire for every animation generated by set of properties. This change is necessary because if we assign the callbacks to only one animation, in case that animation will be cancelled, the other ones won't have any registered callback.

Utils

• makeBoundingBoxFromPoints signature change. The transformation is not supported anymore and requires real points
• removal of all the array utils ( min, max, find those are well covered by es6 now and also is out of fabric scope to provide generic data manipulation utils )
• some utils are considered internal and not exposed anymore ( TODO add list )
• clone and extend have been removed. Those were used in all examples unfortunately so the community has likely adopted them, consider migrating to a well known common library for those functionalities ( lodash, underscore ... ). Avoid using such utilities on classes.
• makeElementSelectable and makeElementUnselectable are removed. Those were needed internally and one of them is still used internally, but is not a fabricJS core functionality and not part of the api anymore.
• exposed sendObjectToPlane, sendPointToPlane, sendVectorToPlane to ease common usages of linear algebra. Check them out, you will benefit from it.
• exposed more vector utils

Misc

• Observable now returns a disposer making it easier to use and the off method redundant #7994
• Point methods #7716 #7709
• Eraser has been extracted to https://github.com/ShaMan123/erase2d
• Touch gestures are not yet migrated/officially supported - use a lib for that for now
• Build pipeline (rollup)
• new testing frameworks (jest, playwright)

[ShaMan123]

• canvas dispose is now async, could be breaking with useEffect in hot reload
• makeBoundingBoxFromPoints(points: Point[]) signature change
• populateWithProperties => pick returns new object
• toJSON should not be used by the dev directly, use toObject #8111
• Text exported styles #8006
• Observable now returns a disposer #7994
• Chaining canvas/object should be regarded as deprecated and unsafe
• Point methods #7716 #7709
• Group #7670

[asturur]

i ll keep formatting the top post to be the reference to read. I ll threat this asyncronously, feel free to continue add known changes if you know them. i was planning to revisit all the PRs and extract

[ShaMan123]

What do you think about planting console.warn in highly breaking stuff that won't surface as errors?

[asturur]

we can with the / dev mode / thing

[ShaMan123]

I think it is better to add an internal util and use rollup to remove console logs or use an env var or something Those comments are useless now, right?

[ShaMan123]

from http://fabricjs.com/v6-breaking-changes:

• dep(Canvas#getCenter): migrate to getCenterPoint #7699
• Promise support #3684 (was it v5? anyways it should be properly documented here and that fromElement and the parser are out of line)
• BREAKING: Object#getObjectScaling, Object#getTotalObjectScaling now returns a fabric.Point instead of {scaleX,scaleY} #7710

[ShaMan123]

• 7776 is not breaking, it saves the dev from a silent breakage that they weren't aware of

• CONCEPT: Group rewrite exposes a change in concept - strict object tree. An object can belong to one parent.

[ShaMan123]

How about we release v6.0.0 with warnings and v6.0.1 without?

[ShaMan123]

Or add an option to config? or both

[asturur]

I think it is better to add an internal util and use rollup to remove console logs or use an env var or something Those comments are useless now, right?

Are useless now but can be activated, can safely become dead code removal with a rollup plugin that swap the comment with a falsy if, with or without an utility to log. Let's keep this thread for logging more than discussing or it get noisy fast

[ShaMan123]

OK I will PR an option I have in mind and we discuss there

[asturur]

OK I will PR an option I have in mind and we discuss there Preferably something at build time, no runtime

[ShaMan123]

Polyline/Polygon/Path _setPositionDimensions => setDimensions #8344

[rogeriochaves]

Group has no longer the method addWithUpdate, only add

[asturur]

From latest TS pr: some chainability removed: setCoords, scale, scaleToWidth, scaleToHeight adjustPosition is gone ( what it was even for? )

Going to update all the upper main description now

[asturur]

BREAKING insertAt signature - (objects, index) => (index, ...objects). Done to comply with the rest of the methods and resemblance to Array.splice BREAKING removed fabric.Collection, but I can put it back

[ShaMan123]

toLocalPoint => controlsUtils.getLocalPoint or unexported normalizePoint

[asturur]

Added all the breaking changes from #8461 and #8519

[asturur]

Need to add the breaking changes from repacking the lib, as soon as export work i can have a full list

[asturur]

Added breakign changes from animation simplification and the removal of canvas aliases on object

[ShaMan123]

This is a great practice, we should stick to it now on for future versions

[ShaMan123]

EraserBrush isn't part of v6 yet, so that is breaking for now #8499

[ShaMan123]

moved to native classes => no more createClass

[ShaMan123]

• no fabric namespace
• CONCEPT: subclassing + classRegistry is now a thing

[linxianxi]

how to set canvas background image in v6?

[maslennikov]

@ShaMan123 experimenting with v6 beta: awesome work, thank you so much for the effort! More straightforward object model and typescript support feels real good.

I understand that a lot is going on with v6 right now but want to provide some hands-on feedback. What I found lacking is reexport of core fabrics types & typing utils (e.g. from typedefs, event typedefs), and of some basic internal building blocks (e.g. to implement custom corner controls logic - resizing instead of scaling - I had to reimplement half of controls supporting code because it is not exported).

[ShaMan123]

Thanks for the feedback. v6 is open for it. We noticed types #8715 etc. Exporting is the one thing that is not stable now and should change. Feel free to open issues.

[bladerunner2020]

how to set canvas background image in v6?

Also wondering how to set background image as setBackgroundImage is not a function any more...

[ShaMan123]

canvas.backgroundImage = imageObject

Open dedicated issues/discussions so we don't pollute this thread. Thanks

[ShaMan123]

setOptions => set

[ShaMan123]

Object#animate accepts only a map of props Object#_animate accepts only a single prop

[ShaMan123]

Anyone struggling take a look at https://github.com/fabricjs/fabric.js/discussions/8739#discussioncomment-5126111

[3400442579]

[ShaMan123]

tree shaking isn't there yet.

[linxianxi]

How is v6 progressing? Could you give us an approximate time for the official version?

[ShaMan123]

@asturur I think it is worth mentioning that since stateful is removed whoever didn't use set relied on hasStateChange and now will find that their app is completely broken. Since we plan to remove set as well I would suggest adding dirty flags (which was what hasStateChanged did) Happy v6 to us all

[ShaMan123]

The prototype doesn't hold defaults anymore, mutation is used only for methods. Change defaults with the static prop ownDefaults or method getDefaults Controls are not shared!

[pixobe]

@ShaMan123 I am building the Master branch locally (V6), type of Image object is randomly generated.
For eg: image$1

   const img = new fabric.Image(image, options);
  console.log(img.get("type");  // image$1

Is there something that am doing wrong?

1. I cloned this repo
2. npm run build:fast or npm run build
3. Linked the package locally to a stenciljs project (that generates web component)

[ShaMan123]

We changed type to be the class name. We didn't take into consideration that rollup, the build tool, will rename the class. You should avoid using type. Use instanceof instead. @asturur

[pixobe]

@ShaMan123 Actually the issue is happening when saving as json/restoring it. And also many of the props are missing while saving for eg: control setting like cornerStyle etc.

I appreciate your time and contribution for open source project.

[ShaMan123]

open an issue with a repro let's discuss there

[ikilane]

please please please, don't forget about rtl support, it's so important to us.

[enriqueerrando]

Hi @ShaMan123, how is everything going? Is there an ETA for the V6?

Thanks in advance!

[ShaMan123]

We are at the finish line

8767 is the last major blocker

No ETA unfortunately Beta is pretty close to the official release. Maybe exports will change a bit (types)

[enriqueerrando]

Ok, thanks for the update!

[vinkovsky]

Hi folks! I am currently working on a react wrapper with Fabricjs v6.

This part is very interesting to me

• canvas dispose is now async, could be breaking with useEffect in hot reload

How do you handle async disposing in a cleanup function? I try different approaches and my code breaks when initializing a canvas that is not yet removed, or the canvas is removed after initialization, so I see a white screen.

Сould you give me some ideas?

[ShaMan123]

A reproduction is valuable. Please open an issue dedicated for this with a repro. Then we can help and solve this.

[vinkovsky]

A reproduction is valuable.

Hello @ShaMan123! Sure, thanks for the reply.

https://github.com/fabricjs/fabric.js/issues/8899

[Sara-Sultan]

I wonder how to use destroy function in group as it is not a function any more. group.destroy();

[ShaMan123]

You can call removeAll and remove it from canvas.