Skip to content
This repository has been archived by the owner on Oct 2, 2020. It is now read-only.

Width size bug #66

Open
tasomaniac opened this issue Jun 6, 2015 · 4 comments
Open

Width size bug #66

tasomaniac opened this issue Jun 6, 2015 · 4 comments
Labels
Milestone

Comments

@tasomaniac
Copy link
Member

screenshot_2015-05-25-09-58-48

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. 😄

@Splaktar Splaktar added the bug label Jun 6, 2015
@Splaktar
Copy link
Contributor

Splaktar commented Jun 6, 2015

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.

@Splaktar Splaktar added this to the 3.0.0 milestone Jun 20, 2015
@Splaktar
Copy link
Contributor

Unfortunately the Angular Material team closed angular/material#2620 as part of their massive bug purges as they shift focus to angular2-material.

@Splaktar Splaktar modified the milestones: Backlog, 3.0.0 Jun 13, 2016
@MichaelSolati
Copy link

This should do the trick...

body {
    word-wrap: break-word;
}

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?

@Splaktar
Copy link
Contributor

@MichaelSolati For general questions about Boomerang and issue triage, please use https://gitter.im/gdg-x/boomerang.

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 free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

No branches or pull requests

3 participants