You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Rails recently introduced a newline after opening <textarea> tag (rails/rails#4000). All browsers ignore this newline.
But rack-test does not. So if the test opens edit page with textarea, and clicks 'Save', then an additional trailing newline is added to the value, sent to the controller and saved to the DB.
This doesn't seem like an issue for Rack-Test, but an issue for Capybara.
Rack-Test is deliberately unaware of browser behavior. It just speaks
HTTP. Capybara would be responsible for simulating the browser in
Rack-Test mode and handing off the correct HTTP-level information to
Rack-Test.
Rails recently introduced a newline after opening <textarea> tag (rails/rails#4000). All browsers ignore this newline.
But rack test does not. So if the test opens edit page with textarea, then clicks save an additional trailing newline is added to the value and saved to the DB.
Rails recently introduced a newline after opening <textarea> tag (rails/rails#4000). All browsers ignore this newline.
But rack-test does not. So if the test opens edit page with textarea, and clicks 'Save', then an additional trailing newline is added to the value, sent to the controller and saved to the DB.
The proof app is here: https://github.com/khustochka/newline_test
It has two integration tests, one driven with Selenium, another with rack-test. The first passes, the second fails.
The text was updated successfully, but these errors were encountered: