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
{{ message }}
This repository has been archived by the owner on Oct 2, 2020. It is now read-only.
When a link in a social stream item is too long, it messes with the width of the page. This may already be fixed. I just want to share the screenshot. 😄
The text was updated successfully, but these errors were encountered:
Thanks for reporting this! This is something that I have been looking at quite a bit today, but never wrote up. I put some details about it here though: angular/material#2620. The behavior is even worse on Firefox. This might be something that can be fixed in angular-material's md-content component.
I looked at making a fix in boomerang, but most options had unacceptable negative consequences like truncating every long line rather than flowing the text, this made most articles unreadable. We could parse through all of the text and look specifically for long links and then either shorten the link name (might be doable with some work) or actually put it through a link shortening API (probably way too slow), but that'll take some time and effort to work out.
But I'm curious how many of these issues that are open are going to be "fixed" for the current angular js app, or are they more concerns for the angular > 2 version??
Like are these issues should be resolved for the current app, or ensure that they are resolved for the upgradeAngular branch?
Once we have the Angular branch production-ready, the plan is to drop support for the AngularJS version of the site. Ideally, any issue fixing and feature enhancement would go into the Angular version.
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
When a link in a social stream item is too long, it messes with the width of the page. This may already be fixed. I just want to share the screenshot. 😄
The text was updated successfully, but these errors were encountered: