Closed chrise86 closed 8 years ago
If only use Semantic UI , have the same issue?
No that's what I mean by switching to the official release. Using the vanilla Semantic UI works fine
@chrise86 I have bump a new version. it wokrs well.
Ah ok cool! :+1: I did try replacing the grid file, I guess I must have needed some others too, thanks! I'll test it out before closing, just incase
I'm using most current version and my grids are not acting properly.
My grid is larger than my body, if I use any standard grid (e.g. ui grid container, ui grid, etc.) Alternatively if I use other types (e.g. ui internally celled grid) the grid is the correct size but then stuff like centered column, row, or grid do not actually center content.
It's very noticeable on mobile..
@chrise86 Do you have tried to use https://github.com/Semantic-Org/Semantic-UI, not the gem?
I'm assuming that was meant for me, no and I do not know how I would deploy to Heroku a rails project that required use of npm.
Can you show me your grid code?
Is it possible to use semantic-ui (not the gem) in a rails project when deploying to Heroku?
I used the gem and https://github.com/Semantic-Org/Semantic-UI/blob/master/dist/semantic.css, got same result.
And the semantic-ui can work on heroku. you can reference http://semantic-ui.com/collections/grid.html
Alright I'm looking into it
update: okay so after going through Bower, buildpacks, etc. I stumbled upon rails-assets gem which is quite simple. A few lines of code is all that is needed and no configuration required for Heroku use. Use 'semantic' package if 'semantic-ui' gives trouble.
Using
The columns should obviously sit next to each other, but instead they sit underneath.
Switching to the official release works fine. It looks like it's to do with the load order. A
.ui.container
rule is overwriting a.ui.grid
rule, forcingdisplay: block;
instead of the requireddisplay: flex;
.Propose to either include 'collections' after 'elements', or simply do not categorise them and load in the order of the official build.