Minor cleanup and maybe minor performance improvements
Minor optimization regarding regexp filtering in timelines
Use strict equality rather than Immutable.is as the compared props are values
Assume children of visible IntersectionObserverArticle always change
This fixes multiple issues, while adding few computations
Revert to using upstream's optimisations
This *does* break things, as `shouldComponentUpdate` assume the
children to never change!
Merge pull request #1148 from ThibG/glitch-soc/merge-upstream
Merge upstream changes
[Glitch] When sending a toot, ensure a CW is only set if the CW field is visible
Partial port of ccc7fe3e1d04c7cabad916e4e57c7739743d5c91 to glitch-soc
It doesn't ensure the field isn't changed, just that it isn't submitted if
the field isn't visible. Ensuring the field isn't changed would require
reworking the “always show CW field” feature.
Merge branch 'master' into glitch-soc/merge-upstream
Optimize makeGetStatus (#11211)
* Optimize makeGetStatus
Because `ImmutableList.filter` always returns a new object and `createSelector`
memoizes based on object identity, the selector returned by `makeGetStatus`
would *always* execute.
To avoid that, we wrap `getFilters` into a new memoizer that memoizes based on
deep equality, thus returning the same object as long as the filters haven't
changed, allowing the memoization of `makeGetStatus` to work.
Furthermore, we memoize the compiled regexs instead of recomputing them each
time the selector is called.
* Fix memoized result being cleared too often
* Make notifications use memoized getFiltersRegex
When sending a toot, ensure a CW is only set if the CW field is visible (#11206)
In some occasions, such as the browser or a browser extension auto-filling
the existing but disabled/hidden CW field, a CW can be set without the user
knowing.
Use ScrollToOptions for smooth scrolling if supported (#11207)
Merge pull request #1146 from ThibG/glitch-soc/merge-upstream
Merge upstream changes
Merge branch 'master' into glitch-soc/merge-upstream
Display FTS warning based on actual search term, not the one being typed (#11202)
Follow-up to #11112