search

arnaudleray / pocketgrid

PocketGrid is a lightweight pure CSS grid system for Responsive Web Design. Moreover, it is semantic, mobile-first, and allows to have an unlimited number of columns and breakpoints.
http://arnaudleray.github.io/pocketgrid/
MIT License
321 stars 48 forks source link

Website is broken? #16

Open Dam-Buty opened 8 years ago

Dam-Buty commented 8 years ago

Hi,

I was window-shopping for a new project of mine, and the PocketGrid website appeared broken in my browser :

image

(up-to-date Chromium on Arch Linux with i3wm, 1201px wide)

Needless to say it doesn't sell the grid system well to see it break on my config :/

Pwired commented 8 years ago

Hi, Did you check it also on another computer/browser ? I haven't seen anything broken on my side, looks the same like always.

Dam-Buty commented 8 years ago

Well for me it is broken on my two different screens (1200+px and 1900+px wide). If i resize the chromium window, it keeps breaking in new and unexpected ways.

I'm not going to run a test suite to determine what is broken, just telling you that if your grid system breaks on standard modern browsers such as Chromium this is going to deter a lot of developpers. Personally i went with another CSS grid framework because if PocketGrid doesn't even work on your own homepage i can only imagine the nightmare of integrating it inside one of my own projects...

hansvanmeteren commented 8 years ago

No problems here (Chromebook, Win10 with FF, Chrome, Edge), no problems on the sites I have built, as far as I can see. No complaints from my clients either until now but of course I don't know which OS they use. Hans

Dam-Buty commented 8 years ago

That's really weird then... What kind of config do you test your framework against?

On my chromebook there is no problem, but no way to have it look good on my work computer. Whatever way i resize my browser window there is overlap and bugginess.

I have no idea what could be causing this, especially when there is nothing outrageously weird about my config. And i've never had this kind of problem with any other grid system so... weird...

I can give more info if needed.

Dam-Buty commented 8 years ago

Possible pointer : i'm using i3-gaps as my window manager, so the browser windows never really have the whole width of the screen. With a 20px gap on each side that leaves 1880px available for Chromium on my 1920-wide monitor. If your grid system relies heavily on standard screen widths then maybe that's the cause of the breakage...

hansvanmeteren commented 8 years ago

To be clear: it's not my system but I have used it on some sites.

I don't think the system relies on standard screen widths (do they exist?) but in percentages of the viewport afaik. I'm no professional and English is not my native langguage which makes it harder to explain, maybe someone else could point you to a possible clue.

I hope so!

Vriendelijke groet, Hans

Hans van Meteren, Numaga Design webontwerp, www.numaga-design.nl, Nijmegen Mobiel te bereiken op: 0651 530 445 ​Alle verdere gegevens: zie ons digitale visitekaartje http://www.numaga-design.nl/pages/visitekaartje.php (OV en adres- / routekaart, Skype, KvK, Leveringsvoorwaarden, BTW). In onze mails genoemde bedragen zijn, tenzij anders vermeld, exclusief BTW.

2016-01-23 13:30 GMT+01:00 Damien BUTY notifications@github.com:

Possible pointer : i'm using i3-gaps as my window manager, so the browser windows never really have the whole width of the screen. With a 20px gap on each side that leaves 1880px available for Chromium on my 1920-wide monitor. If your grid system relies heavily on standard screen widths then maybe that's the cause of the breakage...

— Reply to this email directly or view it on GitHub https://github.com/arnaudleray/pocketgrid/issues/16#issuecomment-174183343 .

dullroar commented 7 years ago

For me it is broken on Firefox 52 on Linux Mint 18.1. Looks just like the problem screenshot above at any window size or browser zoom level. Chromium 56 on same system renders just fine.

dullroar commented 7 years ago

Interestingly enough, the issue is not apparent on FF 52 on Windows, only on my Linux laptop.