-
Notifications
You must be signed in to change notification settings - Fork 824
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Merge pull request #10029 from creative-commoners/pulls/4/titletip
NEW Title tips for form fields
- Loading branch information
Showing
4 changed files
with
95 additions
and
4 deletions.
There are no files selected for viewing
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
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
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1,6 +1,49 @@ | ||
# 4.9.0 (Unreleased) | ||
|
||
## Overview | ||
|
||
## New features | ||
- [Features and enhancements](#features-and-enhancements) | ||
- [Image lazy loading](#image-lazy-loading) | ||
- [Other new features](#other-features) | ||
- [Bugfixes](#bugfixes) | ||
|
||
|
||
## Features and enhancements {#features-and-enhancements} | ||
|
||
### Image lazy loading {#image-lazy-loading} | ||
|
||
Silverstripe CMS now lazy loads most images by default and includes some options to opt-out of this behaviour. | ||
|
||
Image lazy loading defers the loading of images not in the viewport to improve the initial page load performance. | ||
Read more about (image lazy-loading)[https://web.dev/browser-level-image-lazy-loading/]. | ||
|
||
This feature was implemented in partnership with Google. | ||
|
||
Most images will now get the `loading="lazy"` attribute added to them. This includes: | ||
- images added via the HTML Editor's **insert media** button | ||
- image DataObjects added to templates | ||
|
||
Image HTML tags (`<img>`) added in templates will not be lazy loaded by default. | ||
|
||
To disable lazy loading for an individual image in a template, use `$MyImage.LazyLoad(false)`. | ||
|
||
There's some scenarios where you might not want to use the native Silverstripe CMS lazy loading. For example, you might already have a custom lazy loading implementation. | ||
|
||
To opt out of lazy loading globally, use the following yml config: | ||
|
||
```yml | ||
SilverStripe\Assets\Image: | ||
lazy_loading_enabled: false | ||
``` | ||
#### CMS authors | ||
CMS authors can disable lazy loading on images added via the WYSIWYG editor in the "Edit image" panel by setting the new "Loading" field to "Eager". | ||
### Other new features | ||
* [Dot notation support in form fields](https://github.com/silverstripe/silverstripe-framework/pull/9192): Save directly into nested has_one relationships (see [docs](/developer_guides/forms/how_tos/handle_nested_data)). | ||
## Bugfixes {#bugfixes} | ||
This release includes a number of bug fixes to improve a broad range of areas. Check the change logs for full details of these fixes split by module. Thank you to the community members that helped contribute these fixes as part of the release! |
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
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