Are we disregarding the user's layout width preferences if it is set to fluid or just changing the max-width when it is set to fixed?
Are we changing:
.container-limited{max-width:1280px}
to:
.container-limited{max-width:958px}
universally?
Or do I need to create a new .container-xxx class just for the Issues and MR pages? What about the different Merge Request tabs (changes, pipelines, etc)? These require a lot of horizontal space.
Where did 958px come from? That seems awfully specific... Also the width in the example screenshots seem to be around 996px?
Are we disregarding the user's layout width preferences if it is set to fluid or just changing the max-width when it is set to fixed?
We want the Issues and MR discussion can have a limited width of the content, so if it is set to fluid or changing the max-width, the width of content is still 958px.
Are we changing:
.container-limited {max-width: 1280px}
to:
.container-limited {max-width: 958px}
universally?
I think this should be specific to issue and MR pages as @dimitrieh mentioned.
Where did 958px come from? That seems awfully specific... Also the width in the example screenshots seem to be around 996px?
@mikegreiling I believe we should cut scope for now.. as the mr view has unforseen challenges..or at least design challenges that have not been though out. like tabs and diff discussions etc
I think it would be okay to just implement this for issues for now. agreed @hazelyang@tauriedavis ?
Yeah, I think that would be okay. Also, I would be willing to pick this issue up and work on the frontend. I realize that everything may not be defined and it might be easier to play with it in the browser rather than making lots of comps. Feel free to reassign to me, @mikegreiling. If you want to keep working on it, that is okay too :)
Thanks @tauriedavis, I'll reassign it to you. I've got quite a bit on my plate, so if you think you could give this the attention it needs feel free to take it