Farbtastic 2.x is in Alpha, but that doesn't mean we can't investigate its adoption into Drupal 7 core. This also means we can help in its debugging and development.

The whole misc/farbtastic folder should be removed as misc/farbtastic.js is the new location. We don't need the other files anymore because Farbtastic 2 is awesome.

CommentFileSizeAuthor
screenshot34.png47.88 KBrobloach
farb2.patch26.89 KBrobloach

Comments

mfer’s picture

FYI, the big hold up for a farbtastic 2 is IE 6. You can see the problem at http://skitch.com/mattfarina/bj2ru/farbtastic-v2-ie6

IE 6, won't you please go away.

Also, the is canvas based so explorer canvas is needed for IE.

damien tournoud’s picture

I'm not sure that depending on ExplorerCanvas is a good idea either.

mfer’s picture

Version: 7.x-dev » 8.x-dev
Status: Needs work » Postponed

This needs to be pushed out to when we no longer support ie6.

nod_’s picture

Status: Postponed » Active

now is the time.

There is an html5 color input type: #1445224: Add new HTML5 FAPI element: color

I'm for dropping this altogether and let contrib deal with it.

markhalliwell’s picture

Title: Update to Farbtastic 2 » Decide what to do with Farbtastic library
Category: feature » task
Issue tags: -color, -farbtastic

I'm re-purposing this to decide what to do with this ancient library. If we can drop it with #1651344: Use color input type in the color.module, great. If not, we need to decide whether to update or implement a new library.

markhalliwell’s picture

mfer’s picture

FYI, farbtastic isn't being maintained anymore. I say that as the last person to actually maintain it. Someone else either needs to take over maintainership or a migration to something new should happen.

markhalliwell’s picture

Version: 8.x-dev » 9.x-dev
Issue summary: View changes
Status: Active » Closed (duplicate)
Related issues: +#2268955: Deprecate farbtastic library

Looks like we're moving in this direction.

Version: 9.x-dev » 9.0.x-dev

The 9.0.x branch will open for development soon, and the placeholder 9.x branch should no longer be used. Only issues that require a new major version should be filed against 9.0.x (for example, removing deprecated code or updating dependency major versions). New developments and disruptive changes that are allowed in a minor version should be filed against 8.9.x, and significant new features will be moved to 9.1.x at committer discretion. For more information see the Allowed changes during the Drupal 8 and 9 release cycles and the Drupal 9.0.0 release plan.