* Refactor article reactions for increased readability and to insert optimistic rendering later. No functional changes
* Added optimistic rendering
* Fixed comments to fit with style
* Reverts state on error as well
* Set default styles and move button style out of form
* Add MVP of Preact /settings/integrations
* Change background color on hover and focus
* Remove unused constructor
* Improve optimistic rendering
* Add display name
* Use loading indicator for optimistic rendering
* WIP test
* Add basic snapshot tests
* Add HTML variants for cta optimization and other nav bar adjustments
* Fix 1==1 non-random mistake
* Spruce up org call-to-action
* Change default text color
* Add html variant trial and success request specs
* Fix article sidebar caching issue
* One line adjustment
* Modify schema
* Add include ActionView::Helpers::TagHelper to user_tag_spec
* Modify follow_button to remove session context
* Dummy commit
* Change Edit Article to Edit Post
* Dummy commit
* Fix rubocop concerns
* Fix rubocop style
* Resolves#891
* This is applied to root level comments as well as nested replies.
* We are handling latest browsers and special cases for FF, IE8/9/10
* All newer browser except FF support undo/redo functionality in the exact reverse order of text insertion
* Refactored some code
* Support for Bold & Italic text
* Support for Text Links
* In a subsequent change, we can consider adding hotkey for image URL
* Didn't add this feature at the moment since there's no universally accepted key-combination for image URL's that I know of
* IE 8-11 is not supported because it is a bit convoluted and I don't have a way to test it reliably
* We can revisit this if it is really needed and find a jQuery plugin to handle it
* [Fix#909] [ci skip] Added links to testing libraries on testing.md, fixed typo
* Fixed height for READ POST button
* Fixed heigth for READ POST button
* Resolves#245
* This is applied to root level comments as well as nested replies.
* We are ensuring that user has commented at least once which means
they have accepted the code of conduct before
Style changes as per suggestions in code review
* Use full content width (one line with content below)
* Fix gap between actions
* Add hover color and transition for opacity
* Decrease font size a little bit
* Force break "POSTS" and "(123)" into two lines when width is 600-800px
* Add initial remove association feature
* Add initial account deletion feature
* Add back in cursor pointer
* Update email text copy
* Update copy on email html
* Fix nav issue and add integration buttons to account
* Add meta to sidebar and adjust ranking algo
* Update home feed to show more recent posts from folks you follow
* Only show recent posts on home feed if user signed in
Three rules overriding table and cell defaults reduce readability of tables by
1. forcing full width irrespective of actual table contents, and
2. setting an arbitrary width of 1000px on each cell.
This seems to be the result of tinkering to improve table aesthetics by filling horizontal space, but this is a common error that seriously [degrades the readability of tabular data](https://alistapart.com/article/web-typography-tables#section2).
The first issue above is a bit confused: the width has been set to `100%`, and display has been set to `block`.
Setting a default table to 100% width will cause the children to adapt accordingly, achieving the desired result. But changing `table` to `block` breaks the relationship so that the children of the table no longer adapt to the full width. (They behave as though an anonymous parent table of the correct display type has been inserted, while the `table` element behaves like a generic block level element. They no longer will the table, though the table is technically full width.)
This probably explains the arbitrary width on data cells. It's set larger than the container, forcing the browser to resolve it against the available space and thus approximate the expected result of a default table with 100% width.
Rather than trying to fill horizontal space, it's better for readability to allow data cells to adapt to the size of their contents. A better option for aesthetics in blog posts on Dev.to is to remove the three rules deleted here that affect table layout and instead set left and right margins to `auto`, so that narrow tables are centered in posts, but wide tables can still extend beyond the normal content width of paragraphs as they do now.
