Should not apply padding when trimmed (#3858)

Able to set the alpha on Text drop shadows (#3651)

fix doc comments (#3673)

fix unexpected 0 text behaviour (#3650) ...

We got a weird glitch upgrading from pixi 3 to 4, setting the text in a PIXI.Text to 0 results in the label actually saying ' '. This seems like unexpected behaviour considering all the other numbers work :)

Fixed local bounds issue with text (#3633) ...

* Fixed local bounds issue with text

root cause of #3442

* lint..

Merge pull request #3622 from themoonrat/text-drop-shadow-blur-fix ...

Stops shadow blur appearing on the text as well as shadow

Merge pull request #3565 from staff0rd/Text_trim ...

Trimmed text

Ability to set stop points on Text with a gradient (#3576) ...

* Ability to set gradient stop points on Text

* little spacing consistency fix

* Better comparison of arrays

* Made fillGradientStopPoints clear they should be values between 0 and 1

* Potential fix for gradients

* making text with no set stops add the stops manually, so both settings take the same code path

fix type (#3627)

extract trim function to utils

Stops shadow blur appearing on the text as well as shadow ...

Does this by resetting this.context.shadowBlur both if it not required whilst drawing the shadow, and also after drawing the shadow
Fixes: https://github.com/pixijs/pixi.js/issues/3621

move trim to TextStyle

fix method name

added text trimming

Improved documentation ...

Class member documentation improved via removal of unnecessary @memberofs - more members now show up in the docs.
Class getter/setter documentation improved using technique above, and also by removing documentation for setters. Documentation was only showing the setter docs, whereas the getter is where the important information is. JSDoc maintainers themselves recommend just doccing the getter jsdoc3/jsdoc#973
Documented a few classes to let devs know that they are automatically created by PIXI and added to renderer.plugins, like interactionManager and prepare

Fix a bug about compute Text canvas size. (#3519) ...

* Fix a bug about compute Text canvas size.

There are 2 bugs :
* should NOT use `this.context.lineWidth`  before `this.context.lineWidth = style.strokeThickness`.
* the default value of `style.strokeThickness` is `0` , but  `this.context.lineWidth` couldn't be 0 ( in HTML5 , context.lineWidth = 0 will be ignore). So we should NOT use `this.context.lineWidth` for computing size.

* Update Text.js

Don't need  ` + style.strokeThickness` again.

* Update Text.js

* Update Text.js

refactor :   change the  codes of computing `canvas.width` & `canvas.height`  in the same code style.

* use  `style` instead of `this._style`

Merge pull request #3502 from finscn/patch-22 ...

The canvas could be passed into Text

Merge pull request #3513 from pixijs/multi-font-support ...

Adds support for multiple font families

Fixed doc style for typed array

Use `*._texture.*` instead of`*.texture.*` (#3517) ...

It could offer a bit little performance gains.

and in current version  https://github.com/pixijs/pixi.js/blob/master/src/core/text/Text.js#L637  , there is already used `_texture` .
So I think this patch is OK.

Less codes , Less assignment operations. ...

Remove the needless assignment operation.

Adds support for multiple font families

The canvas could be passed into Text ...

This feature could help users to  share canvas among two or more  Text  objects （ like Graphics._SPRITE_TEXTURE in Graphics).

In the game ,normally  we need rebuild stage/scene when stage/scene changed ,  If Text supports passing canvas , we could avoid create and destroy HTMLCanvasElement often when game running. 

e.g. create a canvas-pool  cache some canvas for Text.

Allow '0x' notation of colours via strings to work in Text class (#3341) ...

* Allow strings representing values such as '0xFFFFFF' to be parsed and used by the Text class

* Removed es6 string includes function

Text style fixes (#3405) ...

* Correct reference to default style

* Unit tests for Text Style

Adds quotes around fontFamily (#3352)

Update documentation (#3337) ...

Parameter lines is a string array

fixed settings not being respected (#3315) ...

Discovered that using this kind of code:

```const { MY_SETTING } from settings;```

means that changing settings properties has no effect as the objects
are being set before the user changes them.

Moves constants that are actually settings (#3298) ...

* Made const that are setting writable

* Moved more items to the settings

spelling