Skip to content

Draggable: A small iframeFix refinement #544

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

Closed
wants to merge 1 commit into from

Conversation

atrigent
Copy link

@atrigent atrigent commented Dec 1, 2011

I'm working on an application which has a draggable which adds its droppables in its "start" function. This causes some churn throughout the page and causes the iframes to change their position relative to the "body" tag, which in turn means that the iframe fixes which had been previously added are no longer in the right place. With this change, the user can configure things so that the iframe fixes follow their respective iframes around wherever they move. It fixes the issue I'm encountering with this application, and will result in the same behavior as before if there is no other offset parent than body.

Thanks!

Ari

…s instead of body


This gives the user a measure of control over where the fixes are added - one simply
needs to specify "position: relative" on an ancestor of the iframe and the fix will be put
there. In this way, the iframe fixes can be a little bit more robust when changes to the
page happen which cause the iframes to change their offset on the page.

Things will still break if the iframe changes size or moves within its offset parent.
@atrigent
Copy link
Author

Hi! Is there anything I can do to get this looked at? Would filing a bug report help?

@mikesherov
Copy link
Member

Hi @atrigent, please add some unit tests to your pull requests. This will help get your pull looked at and considered for inclusion in the library. Thanks!

@mikesherov
Copy link
Member

Hi @atrigent, I'm cleaning up the pull request queue right now. Considering this pull request is 11 months old, and doesn't have a ticket that demonstrates the problem, nor unit tests, I'm going to close this for now to keep the queue clean.

I really appreciate the work you've done here, and if you'd still like to pursue this, please file a ticket in the tracker showing the problem, and make sure you run the current test suite, and add new tests that support this change. Thanks!

@mikesherov mikesherov closed this Nov 9, 2012
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

Successfully merging this pull request may close these issues.

2 participants