Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Generate valid clip path id #685

Merged
merged 1 commit into from
Nov 30, 2014
Merged

Conversation

jcamins
Copy link
Contributor

@jcamins jcamins commented Aug 27, 2014

Prior to this patch, if you created a dc chart using a complex selector
like dc.barChart('#area .bar'), the resulting clip path id was invalid:
'area .bar-clip'. This patch replaces spaces, periods, and hash marks
in the id with hyphens to generate a valid clip path id.

Prior to this patch, if you created a dc chart using a complex selector
like dc.barChart('#area .bar'), the resulting clip path id wa invalid:
'area .bar-clip'. This patch replaces spaces, periods, and hash marks
in the id with hyphens to generate a valid clip path id.
@gordonwoodhull gordonwoodhull modified the milestone: v2.0 Sep 29, 2014
@gordonwoodhull gordonwoodhull merged commit b3311ea into dc-js:master Nov 30, 2014
gordonwoodhull added a commit that referenced this pull request Nov 30, 2014
Conflicts:
	src/coordinate-grid-mixin.js
gordonwoodhull added a commit that referenced this pull request Nov 30, 2014
@jcamins, adding a simple test for your PR on clip path id
to make sure it stays fixed and to show the intended behavior
please check and suggest improvements, if any.  Thanks!
@gordonwoodhull
Copy link
Contributor

Thanks @jcamins!

@rpaskowitz
Copy link
Contributor

Any bug fix releases planned for 1.6.0/1.7.0? Just hit this (and thankfully found the fix), but hoping not to need to maintain a branch here with fixes.

@gordonwoodhull
Copy link
Contributor

No I don't plan any bug fix releases on the old versions. There are way too many bugs and it's all I can keep up with to work on 2.0.

I suggest either upgrading to 2.0 when it's finally released in about a month, or forking 1.6/1.7 (only difference being module support) and applying this fix (which should be easy). At least you won't have to worry about keeping it in sync!

@rpaskowitz
Copy link
Contributor

No problem. Good to know the release timeframe for 2.0, already been
playing with it for prototype work.

Decided to work around this for now with some changes to CSS selectors.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants