Skip to content

nbagg issues with ipython 3.0 #3606

Closed
Closed

Description

@tacaswell

This is on both py2k and py3k

  • double clicking kills the interaction
  • the icons are empty blocks

I am having issues down grading to ipython 2.2.0 to see if this is an issue with 3.0 on their side, but am getting 404 errors I don't understand...

Activity

  1. added
    Release criticalFor bugs that make the library unusable (segfaults, incorrect plots, etc) and major regressions.
    on Oct 2, 2014
  2. added this to the v1.4.1 milestone on Oct 2, 2014
  3. tacaswell commented on Oct 2, 2014

    @tacaswell
    MemberAuthor
  4. modified the milestones: v1.4.x, v1.4.1 on Oct 2, 2014
  5. changed the title [-]nbagg is broken[/-] [+]nbagg is broken with ipython 3.0[/+] on Oct 2, 2014
  6. tacaswell commented on Oct 2, 2014

    @tacaswell
    MemberAuthor

    This seems to be issues added on the ipython side. I can reproduce this issue with ipython master branch + 1.4.0, but it works correctly with 2.2.0 + 1.4.x

    cc @takluyver

    3.0 (master branch) + 1.4.0

    ip_nbagg

    2.2.0 + 1.4.x (current maintenance branch)

    ip_nbagg1

  7. changed the title [-]nbagg is broken with ipython 3.0[/-] [+]nbagg issues with ipython 3.0[/+] on Oct 2, 2014
  8. tacaswell commented on Oct 2, 2014

    @tacaswell
    MemberAuthor

    It seems in all cases if you click fast enough things grow confused.

  9. removed
    Release criticalFor bugs that make the library unusable (segfaults, incorrect plots, etc) and major regressions.
    on Oct 2, 2014
  10. takluyver commented on Oct 2, 2014

    @takluyver
    Contributor

    The buttons look like our toolbar buttons, so I'm guessing that some changes to the css are involved. I think we also upgraded the version of fontawesome we use for the button icons, and that necessitated changing the icon names specified in the html. @minrk or @Carreau should be able to give you more details.

  11. added a commit that references this issue on Oct 2, 2014
  12. Carreau commented on Oct 2, 2014

    @Carreau
    Contributor

    Took a stab at it in #3607.

  13. added a commit that references this issue on Oct 2, 2014
  14. pelson commented on Oct 2, 2014

    @pelson
    Member

    It seems in all cases if you click fast enough things grow confused.

    That seems possible (if you have a high latency IPy instance I imagine it is even more pronounced). Does IPy 3 make the situation worse though @tacaswell?

  15. pelson commented on Oct 2, 2014

    @pelson
    Member

    P.S. #3609.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions