Comments (12)
Hey, @Puddingboy !
jQuery was mainly used in current version because JCF heavily relies on DOM and Events manipulations, and of course it helps to support old IE browsers. Now these browsers are dead, so jQuery code could be replaced with much more transparent and shorter one.
There'll definitely be a pure JavaScript implementation without any external dependencies. This way it could be used with any library/framework without any problems.
from jcf.
Any chance a vanilla js version of jcf may pop up in the near future?
from jcf.
Actually there was a vanilla js version of JCF few years ago, but it had its own "jQuery implementation". That implementation was not as good as jQuery and increased amount of js file size. Looks like now we can drop support for IE6-8, so this implementation could be much smaller and performant.
Not sure about nearest future but I think vanilla js version might be released later this year.
Let's keep this issue open until it will be released :)
from jcf.
Any serious issues you are already thinking of in terms of dropping jquery?
from jcf.
We use only several methods from jQuery and if we don't need to support attachEvent
and other stuff we could replace jQuery dependency to the own small core with DOM helper methods. But when jQuery will be available it still could use jQuery, but not sure that this is really needed in case we'll have our own core.
from jcf.
I have a suggestion to push hidden elements further out of the screens view. 4k screens are becoming more common and even if they are invisible I kind of just think it's "right" to push it further away. Maybe assuming 6k would be even better.
I have no science or proof to hold my claim of it being better. I just feel this way, so you can take it with a grain of salt. I play around in dev mode of chrome a lot and when I see this supposedly hidden element on the side it just feels a bit off.
It's a bit comparable with having having a small peel of popcorn behind your teeth and no fiddling can reach it. You know it's there and you can't do anything about it. Or that itch on your back that is just far enough to put your arms in an uncomfortable position... Something along those lines... I suppose it's actually a pretty nasty feeling
from jcf.
@Puddingboy I'm not sure I understand you...
Real form fields are hidden with -9999px
offset. Can you please provide a screenshot with the issue?
from jcf.
My bad for the late response, I had caused that issue myself as I was fiddling around with stuff. It had nothing to do with your code.
I am still giddy waiting for a vannilla js version
from jcf.
I'd love to see a pure JS version as well.
from jcf.
@Puddingboy @patrickcate I'm just curious, what about browser support? Desired IE version?
from jcf.
IE 10 support would be nice, but I'd settle for IE 11.
from jcf.
I kinda wanna vote for IE9+ and want to drop everything before that. That way you can still make use of classList and addEventlistener. I was actually rather disappointed to see that IE8 still holds some marketshare. This way we can make use of:
<!--[if lt IE 9]>
Burn in hell you filthy IE8 peasants!!!
<![endif]-->
I would suggest feature detection as some mobile devices can be quirky. That way we can make use of polyfills where needed.
You would be suprised how often ie9 still pops up in b2b situations. Better to have something that at least works and displays properly. Special features such as css transitions don't need fallback.
from jcf.
Related Issues (20)
- Wrong selectbox rendering after reset form with scrollable.js HOT 1
- full-text search for select box
- Keyboard Tab to switch to next form controll not working
- scrollable looses styling on ios
- Default number input with step 2 on touchpads
- Issue with custom scroll on iOS HOT 1
- programmatically close dropdown when going out of focus HOT 2
- Select options disappear after programmatically trigger hideDropDown HOT 2
- How to unbind element with JCF. HOT 1
- Can I turned off init jcf-scrollable on resize? HOT 1
- How can I do scrollTop? HOT 1
- How to hide the option from JCF dropdown when native select is hidden using method hide() HOT 1
- onchange of select HOT 1
- Have to use small hack with v-model checkboxes on vue.js 2.x HOT 1
- Selection popup dissapears after clicking on dropdown element in Firefox on mobile HOT 1
- How can I close select dropdown programmatically? HOT 2
- compatibility jquery 3
- How to exclude elements from rendering HOT 1
- Ajax loading HOT 3
- JCF js library does not allow smartphone wheels (IOS device ) on multiple selection select fields
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from jcf.