Oh, I’d get the point, I have seen it before, I just chose to ignore it cause it really didn’t address the point I was making 
And as much as I appreciate your opinion Freshface (I do hate using Pseudonym’s), comparing developing for Responsive Design to the point I was making, are rally miles apart
The fact remains, not all of the coding is compatible with the browsers it clearly states, we can argue all day about standards , whats perceived as acceptable, and whats not ( which I might add are you will have as many agree and disagree ), but to reiterate, it should not state that the website (which incorporates all element of the website) is compatible with a browser that its not ….
Thats my opinion, professionally, as a customer, or whatever way you want to take it
I still think my initial question was a fair one, I hasten to add I don’t think for a second that a Envato member of staff will answer it
I will also add, I aint having a go at the authors in relation to these templates, but I will also add one more thing
The really top authors in Themeforest, we all know who they are, would never ever use transitions without having some fallback in place, and would not use transforms and state its compatible with xy browser when its not.
Thats regardless of whats generally accepted as you state
Anyway, it looks like I am fighting a losing battle here
, not the first time and wont be the last
Regards
J
bitfade said
Johnny4B saidwhat i meant was: if transitions in ie are crucial to you, just ie check the preview to make sure a js fallback is present.
I don’t need to check it, I know it wont work
Well, two of them also use 3D tranforms, no JS fallaback is going to help there
But that’s a different thread for a different day 
bitfade said
IE9 doesn’t support css transitions. Without a js fallback, that means no fade but on/off for an hover transition. That doesn’t qualify as major issue in my book: as long as all elements are correctly placed/formatted, the template/theme is ie compatible. If that’s not the case for you, just ie check the preview before purchasing it.
I don’t need to check it, I know it wont work
And further more, I wasn’t buying the template, I was merely asking why they got approved
As it happens, the CSS fallback implemented in two of three, totally detracts from the look of the templates in question.
No it does not effect the structure of the websites. but it does the look ,and once again I’ll state that he majority of websites bought here would be down to looks with more customers *
Anyway, this is turning into a points scoring contest and this stage, and well I aint really up for that.
I suppose, with you in particular, we will have top agree to disagree
- I imagine
rvision_ said
Johnny4B saidThen make it compatible in xy browser.
Well Eugene, all I know is, if I showcase a prototype of a website for a client and they are paying for that work, and I tell them its compatible in xy browser, and it is not, then I aint doing my job correctly
Well, that’s the point, I wouldn’t, I was using it as an example …. A sort of comparison to the fact of my original point
You couldn’t see that, or are you trying to be smart and failing miserably
Most WP themes will come with one of the standard e-commerce solutions, like woo-commerce
And yes, with most of them you don’t have to ingrate a payment terminal, most can process the transactions without payment.
bitfade said
and you’ll see more and more of them because devs just got sick of implementing jquery fallbacks to support old ie crap. Compatible doesn’t mean optimized for and, as long as layout is good, i don’t see any issue with it.IE was hardly ever able to run anything super duper, not to mention its memory leaks eating ram for breakfast when using even the simplest js code.
Users want all the eye candy ? then they can install a real browser.
Old ie crap, we are taking about ie9, who is using ie10, nobody that has not upgraded to W8, that’s for sure
And just to add, I imagine the majority of Envato customers, particularly with Themeforest, buy the templates based on aesthetics more than anything else.
They couldn’t give a damn how its built, or what structure it has
Well Eugene, all I know is, if I showcase a prototype of a website for a client and they are paying for that work, and I tell them its compatible in xy browser, and it is not, then I aint doing my job correctly
Why should it be any different for a web portal such as Envato to allow their customers, of many who dont code, buy a template that is not compatible with the browser it states.
I aint having a go at the authors (to a degree ,although the three i have seen have been from fairly new authors), but its products being sold that don’t fulfill their description
If people think that fine, well I disagree, maybe its just different perspective on what you are delivering to clients, or in Envato’s case, their customers
What, are you for real
The structure, you think most people buy websites for the structure, give me a break
The websites are using a transition that is not working in a browser it states it works in, why does it matter, cause some poor gobsh**E is going to buy said template and then complain and question why the super dooper effect on the front of his website does not work anymore
Thats why it matters
Why are so many websites getting through as ie-7 to ie-9 compatible when they clearly are using CSS transitions.
I have seen three websites in the recent two weeks with almost identical circular transitions ON THE FRONT PAGE getting passed by verification for ie-7 -9 !!!
Are the powers that verifying not doing their job correctly.
Just thought I’d ask
Regards
J
