Skip to content
View in the app

A better way to browse. Learn more.

Web Designer Forum

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.

Other browsers might impliment -webkit-

Featured Replies

Has anyone seen this? There was a discussion about a week ago for other browser (Mozilla, Opera etc) to start implimenting -webkit-* styles because they have "no other option" - there are apparently so many websites out there (especially for the mobile web) that are webkit-only websites. Even though other prefixes exist and the styles work essentially the same, web authors don't tend to impliment them because their mobile market share is almost non-existant.

 

If you're looking for more information about the issue, start with Christian Heilmann's post about it - he's got a few useful links including the notes from the meeting?

 

What can we do about this? I think we should all be aware of this and flag it up whenever someone posts a link to a site or any code that only uses -webkit-* styles. Does anyone else have any thoughts?

A member posted this in the status updates section a couple of days ago.

 

There are a few ways of thinking about it. One is that vendor prefixes are creating a segmented web, web kit may introduce new things at a more accelerated rate now so as to stay ahead of other browsers, this could lead to the implementation of bloated useless prefix additions. Not to mention that this deviation away from standards will go someway towards creating a broken web. Thing is that it takes so long to ratify a new standard that I'm not surprised vendor prefixes exist, otherwise advancements in web design would remain years behind what was actually possible.

 

Ideally I'd like to see an easier, leaner way to have new standards implemented.

Edited by MikeChipshop

Honestly, I just want all browser makers to agree on how to implement each CSS3 rule and just drop prefixes. It's asinine that we still have to include prefixes at all.

 

However, webkit has the most robust CSS3 implementation so if they want to take the webkit approach and drop the others I'm fine with it, as long as they just drop prefixes altogether.

Seems like a good idea at first (and if it wasn't for the pit-falls i'd give it a +1) but how would we iron out the inevitable browser inconsistent rendering?

 

Shame MS don't install Chrome Window into all older versions of IE as an update. That would help a bit.

 

It would also help if the W3C would stop faffing about and get their collective arses into gear over HTML5 and CSS3. Been on the drawing board longer than a UK government project.

 

CSS3 is like some coding Hokey-Cokey at the moment.

 

You put your declaration in,

you take your declaration out.

In, out, in out,

Vendor prefixes all about.

because their mobile market share is almost non-existant.

 

What people forget (because iOS is the sexy platform to develop for) is that the largest mobile engine is actually Presto (Opera, Nintendo DS).

Edited by Renaissance-Design
cf. correction below

  • Author

I'm gonna refer everyone to this (also, Webmonkey's back - how awesome is that?)

 

Webkit isn't breaking the Web, you are.

That post sums up my feelings perfectly. The issue is that some demos only show the -webkit- styles when Gecko, Presto and Trident have the ability to do most of the stuff as well, the users try the site in their iPhone and see that it's awesome, so assume it's awesome everywhere. It's starting to get to the state where "This website is best viewed on a iPhone" will be popping up under the splash-page :(

 

Good shout on the popularity of Presto - I'd forgotten that Opera Mobile has been around for so long

Create an account or sign in to comment

Account

Navigation

Search

Search

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.