cross browser

[xinjia]

---

mga master unsay pama agi anang pag code html / css unya compatible na siya sa lain browser, kay ang senario
ok sa firefox unya sa chrome ug ie etc. guba man, unsa mga maaung giya nga atung sundon ani?

[cebugdev]

pangitaa asa sa mga element na imo gigamit ang wala ni work sa ubang browser, nya tan.awa unsa na CSS element version na cla kay ang rason dli na mowork kay basin dli supported ang version sa kana na browser.

dapat naka decide na ka daan unsa na browser version ang minimum support nmo, then gamita ang CSS specific na version ana.

[boang3000]

pangitaa asa sa mga element na imo gigamit ang wala ni work sa ubang browser, nya tan.awa unsa na CSS element version na cla kay ang rason dli na mowork kay basin dli supported ang version sa kana na browser.

dapat naka decide na ka daan unsa na browser version ang minimum support nmo, then gamita ang CSS specific na version ana.

+ 1 to this or gamit ka og 960grid or laing framework sa CSS pra dali ra haha

[noy.juan]

the term cross browser should not be used anymore AFAIK since most browser are built in layout engine... for example google chrome, safari, midori, epiphany and last i heard opera are based from webkit layout engine, so your design should be aimed towards that... you can use the vendor specific -webkit, firefox is using gecko layout engine, based from original netscape layout engine, vendor specific s -moz, ie however is different since it uses proprietary engine layout i think the current one is using trident...

to really support multiple engine layout one should declare its vendor specific prefix to have better support

border-radius:2px; <-- official css property
-moz-border-radius:2px;
-webkit-border-radius:2px;
-o-border-radius:2px; <--- for old opera browser
-khtml-border-radius:2px; <--- for konqueror browser

[andrex]

the term cross browser should not be used anymore AFAIK since most browser are built in layout engine... for example google chrome, safari, midori, epiphany and last i heard opera are based from webkit layout engine, so your design should be aimed towards that... you can use the vendor specific -webkit, firefox is using gecko layout engine, based from original netscape layout engine, vendor specific s -moz, ie however is different since it uses proprietary engine layout i think the current one is using trident...

to really support multiple engine layout one should declare its vendor specific prefix to have better support

border-radius:2px; <-- official css property
-moz-border-radius:2px;
-webkit-border-radius:2px;
-o-border-radius:2px; <--- for old opera browser
-khtml-border-radius:2px; <--- for konqueror browser

TS kani ka boss @noy.juan sakto ni siya. Also take note ts ang layouts nimu kay basin imung layouts is dili sakto pag ka structured. Mostly for old IE ky ang mga floats ug positions ang problema. Pero if for latest browsers kay usually the same na lang na sila ug naa pud parehas sa gi ingon ni boss @noy.juan na css na engine specific.

IE 9+, Firefox latest ug chrome latest usually parehas nana sila dili na dapat maguba kaayo imong layout. Pwera na lang na sa pixal difference nila na 1 ~ 2px na ma notice nimo pero sa ordinary users dili na ma notice.

[xinjia]

thnks... suwayan

[noy.juan]

its better to reset all DOM css before starting your main css code... atleast it evens the playing field on other browser...

[exequtor]

@TS, I suggest you use a CSS framework like Twitter's Bootstrap. It'll save your time, and no more headaches.

[andrex]

@TS, I suggest you use a CSS framework like Twitter's Bootstrap. It'll save your time, and no more headaches.

Pwede rasad ka ani TS pero if ganahan jud ka makat-on imo jud nang e mano mano para masabtan jud nimo.

[noy.juan]

i recommend not using framework unless necessary... kay ug maanad gani ka... malas nimo... kutob ra jud ka sa mga framework...