css errors

General discussion of development ideas and the approaches taken in the 3.x branch of phpBB. The next feature release of phpBB 3 will be 3.3/Proteus.
Forum rules
Please do not post support questions regarding installing, updating, or upgrading phpBB 3.2.x. If you need support for phpBB 3.2.x please visit the 3.2.x Support Forum on phpbb.com.

If you have questions regarding writing extensions please post in Extension Writers Discussion to receive proper guidance from our staff and community.
Post Reply
marian0810
Former Team Member
Posts: 16
Joined: Sun Jul 25, 2010 11:31 am
Location: The Netherlands
Contact:

css errors

Post by marian0810 » Tue Sep 23, 2014 2:41 pm

Possibly a bit of an ocd question but are there plans to fix any current css errors before the stable release?

http://jigsaw.w3.org/css-validator/vali ... Findex.php

FYI I just updated 3 testforums to RC4 and they all show the exact same errors.
Don' t Cry Because It's Over
Smile Because It Happened

User avatar
callumacrae
Former Team Member
Posts: 1046
Joined: Tue Apr 27, 2010 9:37 am
Location: England
Contact:

Re: css errors

Post by callumacrae » Mon Sep 29, 2014 5:18 pm

There's nothing wrong with the CSS. There's a reason nobody uses the validators anymore :)
Made by developers, for developers!
My blog

User avatar
Arty
Former Team Member
Posts: 985
Joined: Wed Mar 06, 2002 2:36 pm
Location: Mars
Contact:

Re: css errors

Post by Arty » Mon Sep 29, 2014 10:09 pm

None of those errors are errors.

Error #1: validator sucks. pointer-events does exist. All modern browsers support it, even IE.
Error #2: validator sucks. There is absolutely nothing wrong with syntax.
The rest of errors: IE sucks. That's CSS for gradients in IE below 10.

Warnings: bunch of nonsense. It can't recognize vendor prefixes.

User avatar
BioLogIn
Registered User
Posts: 28
Joined: Mon Dec 10, 2012 6:55 pm

Re: css errors

Post by BioLogIn » Tue Oct 07, 2014 4:30 am

validator sucks
With all due respect, validator just does what it was designed to do - checks pages for HTML standards conformance. So what you want to say is that W3C's HTML standards are outdated (and therefore suck). Which is also a very debatable topic.

User avatar
VSE
Extension Customisations
Extension Customisations
Posts: 670
Joined: Mon Mar 08, 2010 9:18 am

Re: css errors

Post by VSE » Tue Oct 07, 2014 5:16 am

BioLogIn wrote:With all due respect, validator just does what it was designed to do - checks pages for HTML standards conformance. So what you want to say is that W3C's HTML standards are outdated (and therefore suck). Which is also a very debatable topic.
Not even that though. It's just that the W3C spec for CSS3 is underdeveloped. It does not support vendor prefixes, for example, because strictly speaking they are not in the spec yet, but they are implemented by the browser vendors. There's a ton of legal CSS implemented by browsers already, that has not yet been added to the W3C's spec as a standard yet, so it's not that the W3C is outdated...it's pre-dated...it's very behind the times.
Has an irascible disposition.

User avatar
callumacrae
Former Team Member
Posts: 1046
Joined: Tue Apr 27, 2010 9:37 am
Location: England
Contact:

Re: css errors

Post by callumacrae » Tue Oct 07, 2014 8:20 am

BioLogIn wrote:
validator sucks
With all due respect, validator just does what it was designed to do - checks pages for HTML standards conformance. So what you want to say is that W3C's HTML standards are outdated (and therefore suck). Which is also a very debatable topic.
I think you're confusing HTML and CSS, because I never mentioned the HTML validator :)

The HTML validation is even worse, though. It just shouldn't have a validator. Web Components have a specification, yet cause the HTML validator to fail.
Made by developers, for developers!
My blog

User avatar
BioLogIn
Registered User
Posts: 28
Joined: Mon Dec 10, 2012 6:55 pm

Re: css errors

Post by BioLogIn » Wed Oct 08, 2014 7:03 am

Yeah, CCS standards, not HTML. My apologies for the typo. Doesn't change my meaning, though. I, personally, would rather rely on (outdated) standards, than to use some vendor-specific specs that could become obsolete in a few years. But I guess that's just me.

User avatar
hanakin
Front-End Dev Team Lead
Front-End Dev Team Lead
Posts: 906
Joined: Sat Dec 25, 2010 9:02 pm
Contact:

Re: css errors

Post by hanakin » Wed Oct 08, 2014 6:09 pm

BioLogIn wrote:Yeah, CCS standards, not HTML. My apologies for the typo. Doesn't change my meaning, though. I, personally, would rather rely on (outdated) standards, than to use some vendor-specific specs that could become obsolete in a few years. But I guess that's just me.
thats what build tools and processes are for. I never write anything except official syntax!
Donations welcome via Paypal Image

User avatar
callumacrae
Former Team Member
Posts: 1046
Joined: Tue Apr 27, 2010 9:37 am
Location: England
Contact:

Re: css errors

Post by callumacrae » Thu Oct 09, 2014 12:41 pm

https://github.com/postcss/autoprefixer
https://leaverou.github.io/prefixfree/

autoprefixer is better, but prefixfree is prettier
Made by developers, for developers!
My blog

Post Reply