| Commit message (Collapse) | Author | Age | Files | Lines |
|\
| |
| | |
Prevent ujs event propagation if element disabled when event chain begins
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
The existing UJS event behavior relies on browsers not sending events for
various events when an element is disabled. For example, imagine the following:
<button type="submit" disabled="disabled">Click me</button>
The above button is disabled, so browsers will not trigger a click event and
all UJS behavior is prevented. However, imagine a button like this:
<button type="submit" disabled="disabled"><strong>Click me</strong></button>
The above is treated differently by browsers such as Chrome/Safari. These
browsers do not consider the strong tag to be disabled, and will trigger click
events. UJS has logic to walk up the DOM to find an associated element subject
to UJS behavior. But, this logic does not take into account the disabled
status of the element.
I originally thought we could simply change the selectors used to match
elements to ignore disabled elements. However, UJS disables some elements as
part of the event chain. So, an element might match early in the chain and
then fail to match later. Instead of changing the selectors I added a callback
to the chain that calls `stopEverything` if an element is disabled when the
event chain begins.
|
|\ \
| | |
| | | |
ignore system test gems on Gemfile when execute with --skip-test option
|
| | | |
|
| | | |
|
| | |
| | |
| | |
| | |
| | |
| | | |
This is a follow up to a6d065e. When using `form_with` you must supply
field ids manually. Since the scaffold generator is using labels we
need to make sure that they are linked up properly.
|
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
"3 Days before release" should an h2, like the rest of the day headings.
All of the steps are h3 tags.
[ci skip]
|
| | |
| | |
| | |
| | |
| | |
| | | |
Add apostrophe.
[ci skip]
|
| | |
| | |
| | |
| | |
| | |
| | | |
Add necessary commas.
[ci skip]
|
| | |
| | |
| | |
| | |
| | |
| | | |
Taken from `bin/rails about` run on a v5.1.0.rc1 application.
[ci skip]
|
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
RC1 is out, `5-1-stable` has been created, figured it was time to start
updating this stuff :)
[ci skip]
|
| | |
| | |
| | |
| | | |
[ci skip]
|
|\ \ \
| | | |
| | | |
| | | |
| | | | |
y-yagi/rename_local_current_user_to_verified_user_guide
Rename local variable name `current_user` to `verified_user` [ci skip]
|
|/ / /
| | |
| | |
| | | |
Related #28570
|
|\ \ \
| | | |
| | | | |
Rename local variable name `current_user` to `verified_user` [ci skip]
|
|/ / /
| | |
| | |
| | |
| | | |
Assigning local variable named `current_user` in the condition is
confusing.
|
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
This reverts commit 296d024b4e91c4891ae0b010249193513e63b921, reversing
changes made to e341d835070c7ef9990f41e02bbf46536be0aee7.
We aren't trying to compare to current_user, we're assigning that variable.
|
|\ \ \ |
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
config.time_zone is no longer in included in config/application.rb.
See 28dcadc0140dfdebe87d5e691fd709c0a9ae0bae.
|
| | | | |
|
|\ \ \ \
| | | | |
| | | | | |
Update Action Cable README.md - typo fix [ci skip]
|
| | | | | |
|
|\ \ \ \ \
| |/ / / /
|/| | | | |
Fix doc format for `duplicable?` [ci skip]
|
|/ / / / |
|
| | | | |
|
|\ \ \ \
| | | | |
| | | | | |
Remove unnecessary ruby version comments
|
|/ / / / |
|
|\ \ \ \
| | | | |
| | | | |
| | | | |
| | | | | |
rachel-carvalho/update_browser_compatibility_for_http_verbs
Update guide to reflect browser compatibility for HTTP verbs
|
| | | | | |
|
|\ \ \ \ \
| |/ / / /
|/| | | | |
Additional explanation about cache implementations
|
|/ / / / |
|
|\ \ \ \
| | | | |
| | | | | |
Bump Travis ruby version to 2.4.1
|
| | | | |
| | | | |
| | | | |
| | | | | |
https://www.ruby-lang.org/en/news/2017/03/22/ruby-2-4-1-released/
|
|\ \ \ \ \
| | | | | |
| | | | | | |
Fix duplicable? for Rational and Complex on ruby master, since they are now duplicable
|
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
duplicable
|
|\ \ \ \ \ \
| |/ / / / /
|/| | | | | |
Move comment to inside the method [ci skip]
|
|/ / / / /
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
Because this comment is not document for `supports_ranges?`
ref: https://github.com/rails/rails/pull/27636#discussion_r107560081
|
|\ \ \ \ \
| |_|_|/ /
|/| | | | |
Remove `CollectionProxy#uniq`
|
|/ / / /
| | | |
| | | |
| | | |
| | | | |
Since #28473 `uniq` is delegated to `records`, so `CollectionProxy#uniq`
is unnecessary.
|
|\ \ \ \
| | | | |
| | | | | |
Document AC::Connection::Authorization#reject_unauthorized_connection
|
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
This method is repeatedly used throughout the docs (in the [AC::Connection docs](https://github.com/rails/rails/blob/12b684985837bc8ee9ad15c174cf4e07ca82d7c4/actioncable/lib/action_cable/connection/base.rb#L28), the [AC README](https://github.com/rails/rails/blob/12b684985837bc8ee9ad15c174cf4e07ca82d7c4/actioncable/README.md#a-full-stack-example), the [AC Guides](https://github.com/rails/rails/blob/12b684985837bc8ee9ad15c174cf4e07ca82d7c4/guides/source/action_cable_overview.md#connection-setup)), but not actually documented itself and seemingly not supported for public use based on its current `private` status.
This actually makes the method public and documents it. The actual behavior that’s documented here is implemented [here](https://github.com/rails/rails/blob/12b684985837bc8ee9ad15c174cf4e07ca82d7c4/actioncable/lib/action_cable/connection/base.rb#L213-L219), via [this rescuing of the UnauthorizedError](https://github.com/rails/rails/blob/3dd1de8ba4d5862b01e7f5dd3878b21fd98b443b/actioncable/lib/action_cable/connection/base.rb#L172).
The method is [already tested here](https://github.com/rails/rails/blob/25473baf409185638073fe2f016f4b9dda284e50/actioncable/test/connection/authorization_test.rb#L17-L29).
|
|\ \ \ \ \
| | | | | |
| | | | | | |
List options for `rails new --webpack=WEBPACK`
|
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
When you type `rails new -h`, the `--database=DATABASE` options display
this useful message:
> Preconfigure for selected database (options: mysql/postgresql/sqlite3/oracle/frontbase/ibm_db/sqlserver/jdbcmysql/jdbcsqlite3/jdbcpostgresql/jdbc)
However, the `--webpack=WEBPACK` option only displays this:
> Preconfigure for app-like JavaScript with Webpack
so it's hard to know *which* values are valid for `WEBPACK`.
This commit improves the help message to display:
> Preconfigure for app-like JavaScript with Webpack (options: react/vue/angular)
The implication of this commit is that the list needs to be manually updated
whenever rails/webpacker adds support for a new framework.
However, I don't imagine this list to change very frequently, and I think that
the benefit of display the list to the users is greater than the hustle of
updating the list when needed.
|
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
[ci skip]
|
|\ \ \ \ \ \
| | | | | | |
| | | | | | | |
Change AD::ParamsParser::ParseError deprecation so it can be rescued
|
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | | |
Fixes #28525
|
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | | |
An alternative to DeprecatedConstantProxy which works more transparently
with exceptions because it returns the object that the new constant
refers to rather than a proxy. This is then compatible with
`rescue OldException`.
|
|\ \ \ \ \ \ \
| | | | | | | |
| | | | | | | | |
Correctly reset ARGV for "rails runner `CODE' arg arg arg..."
|
| | | | | | | | |
|
| |/ / / / / /
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | | |
The code itself should not be in the ARGV vector.
Fixes #28515
|