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

[Popup] Possible error in popup module's supports.svg() function #5360

Open
davidlav opened this issue May 11, 2017 · 4 comments
Open

[Popup] Possible error in popup module's supports.svg() function #5360

davidlav opened this issue May 11, 2017 · 4 comments

Comments

@davidlav
Copy link

In trying to get Semantic UI popups to work on d3 elements, I found a possible error in the function that checks for browser support of SVGGraphicsElement.

A prior bug report (#3043) explained that Semantic UI checks for browser support of the SVGGraphicsElement before allowing a popup over one to be created. I believe the current function returns the opposite of what it ought to:

supports: {
          svg: function() {
            return (typeof SVGGraphicsElement === undefined);
          }
        }

The above function returns false when SVGGraphicsElements do exist. The equality operator should be an inequality operator instead.

supports: {
          svg: function() {
            return (typeof SVGGraphicsElement !== undefined);
          }
        }

When I change === to !== my popups are created and work as they should.

@awgv awgv added this to the Needs Milestone milestone May 11, 2017
@awgv
Copy link
Member

awgv commented May 11, 2017

Hi @davidlav, thank you, the maintainer will take a look. Linking the original issue here: #3043.

@Tweety79rw
Copy link

I noticed this bug September 2016, but I guess I didn't follow the contributing guide well enough. Here is the pull request #4517

@awgv awgv changed the title Possible error in popup module's supports.svg() function [Popup] Possible error in popup module's supports.svg() function Jun 2, 2017
@stale
Copy link

stale bot commented Jun 5, 2018

There has been no activity in this thread for 90 days. While we care about every issue and we’d love to see this fixed, the core team’s time is limited so we have to focus our attention on the issues that are most pressing. Therefore, we will likely not be able to get to this one.

However, PRs for this issue will of course be accepted and welcome!

If there is no more activity in the next 90 days, this issue will be closed automatically for housekeeping. To prevent this, simply leave a reply here. Thanks!

@stale stale bot added the stale label Jun 5, 2018
@lubber-de

This comment was marked as spam.

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

No branches or pull requests

4 participants