Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Panel content fills only half the available space #35

Open
sandnath opened this issue Jul 27, 2016 · 5 comments
Open

Panel content fills only half the available space #35

sandnath opened this issue Jul 27, 2016 · 5 comments

Comments

@sandnath
Copy link

Hello,
First of all - great work and I loved this. Just one issue for now... How do I fill up the whole content with text? It always only fills half of it - does not matter html content or simple text.

What changes need to be done in css or any other place to achieve this?

Here is a picture
tl-1
...

@rpocklin
Copy link
Owner

Thanks for the picture, so much easier to understand than describing it.

You decide what content goes in the timeline event, there's no requirement to limit yourself to the directive I wrote. Likewise you can go for it with the CSS to maximise the space. I could possibly add a class="fluid" option to make it expand to fill the container, if others would like it too.

@sandnath
Copy link
Author

Thanks so much for the response. Can you please elaborate with little bit more code? I am not too conversant with css but I can hack better if you please help. Appreciate it!

@rpocklin
Copy link
Owner

rpocklin commented Aug 9, 2016

I have fixed this in master, I will release it soon.

@pdemilly
Copy link

pdemilly commented Oct 10, 2016

I just tried it with master and it is still not filling the whole width and the timeline icons are not lining up with the edge when using either right or left. Any suggestion on how to remove that unused space.

Thanks

@bentrm
Copy link

bentrm commented Feb 10, 2017

Using class names instead of the directives tag names in the stylesheets fixed this for me. Pretty much the same changes that are suggested in #36.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants