| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
- Auto-generating content from the filename of an image is not suitable
alternative text; alt text that isn't fully considered can be
distracting and fatiguing for screen readers users (blind, low vision,
dyslexic people).
- Setting a filename fallback short circuits screen reader default
behavior and configuration for blank descriptions.
- Setting poor defaults also creates false negatives for accessibility
linting and testing software, that makes it harder to improve
application accessibility.
***
- After this change, if authors leave images without alt text, screen
readers will fallback to default behavior for missing alt text.
- Also with this change, Automated linting and testing tools will
correctly generate warnings.
[Fixes #30096]
|
|
|
|
|
|
| |
Changed sentence to be more clear
[ci skip]
|
|
|
|
|
|
| |
`it` and `has` are for singular, not plural
[ci skip]
|
|
|
|
|
|
| |
Periods should be outside of the <a> tags
[ci skip]
|
|\
| |
| | |
Update guides/source/plugins.md [ci skip]
|
| | |
|
|/ |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|\
| |
| | |
Improve callback examples in Active Job guide
|
| | |
|
| |
| |
| |
| | |
The advice for symbol/block form is taken from the Active Record guides.
|
|\ \
| | |
| | | |
Fix generator example code [ci skip]
|
| | | |
|
|/ / |
|
| | |
|
|\ \
| | |
| | | |
add reload_association to documentation
|
| | | |
|
| | | |
|
|/ /
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
In some examples and guides we are recommending to use code like:
```ruby
verified_user = User.find_by(id: cookies.signed[:user_id])
```
My suggestion is to use instead:
```ruby
verified_user = User.find_by(id: cookies.encrypted[:user_id])
```
which invites users to prefer the "newer" encrypted cookies over the
"legacy" signed cookies.
|
| |
| |
| |
| |
| |
| |
| | |
Should _probably_ be done across the board with all of our
documentation, but going to leave that for another time :)
[ci skip]
|
| |
| |
| |
| | |
[ci skip]
|
|/
|
|
| |
work as intended. [ci skip]
|
| |
|
| |
|
|
|
|
|
| |
It seems that it accepts only HTTPS connections.
Ref: https://github.com/postgres/postgres/commit/7f77cbd996855a06fb742ea11adbe55c42b48fe2
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
commit 4a3d295f3011e771cddead80de7497ca15d15c13
Author: Yauheni Dakuka <yauheni.dakuka@gmail.com>
Date: Fri Jul 28 14:31:35 2017 +0300
Update routing.md
commit 620a4ce47288e3ef6504290c78f931214968e7e3
Author: Yauheni Dakuka <yauheni.dakuka@gmail.com>
Date: Fri Jul 28 14:19:29 2017 +0300
[ci skip] update routing guide
|
| |
|
|
|
|
| |
Pointing at Rails master generally requires pointing at Arel master
|
|
|
|
| |
callbacks
|
|\
| |
| | |
Updates Rails upgrade guide on `ActionView::Helpers::RecordTagHelper`
|
| |
| |
| |
| | |
`ActionView::Helpers::RecordTagHelper`
|
|\ \
| | |
| | | |
Fixing "Adding Member Routes" documentation
|
| | |
| | |
| | | |
Previously said the helpers were preview_photo_url and preview_photo_path, i.e. action_resource, when in fact they are resource_action. i.e. photo_preview_path. Fixed.
|
|\ \ \
| | | |
| | | | |
Add documentation for class_attribute default option
|
| | | | |
|
|\ \ \ \
| | | | |
| | | | | |
Set `represent_boolean_as_integer` via `configuration`
|
| | | | | |
|
|/ / / / |
|
|\ \ \ \
| | | | |
| | | | | |
Fix boolean column migration script
|
| | |_|/
| |/| | |
|
| | | |
| | | |
| | | |
| | | | |
basis that if it was simple, the user wouldn't be reading the docs
|
|/ / / |
|
|\ \ \
| | | |
| | | | |
Change sqlite3 boolean serialization to use 1 and 0
|
| |/ /
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Abstract boolean serialization has been using 't' and 'f', with MySQL
overriding that to use 1 and 0.
This has the advantage that SQLite natively recognizes 1 and 0 as true
and false, but does not natively recognize 't' and 'f'.
This change in serialization requires a migration of stored boolean data
for SQLite databases, so it's implemented behind a configuration flag
whose default false value is deprecated. The flag itself can be
deprecated in a future version of Rails. While loaded models will give
the correct result for boolean columns without migrating old data,
where() clauses will interact incorrectly with old data.
While working in this area, also change the abstract adapter to use
`"TRUE"` and `"FALSE"` as quoted values and `true` and `false` for
unquoted. These are supported by PostreSQL, and MySQL remains
overriden.
|
|/ / |
|
| |
| |
| |
| |
| |
| |
| |
| | |
Rather than protecting from forgery in the generated
ApplicationController, add it to ActionController::Base by config. This
configuration defaults to false to support older versions which have
removed it from their ApplicationController, but is set to true for
Rails 5.2.
|