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

Fix Tooltip on disabled button #4865

Merged
merged 4 commits into from
Feb 16, 2017
Merged

Conversation

@mention-bot
Copy link

@afc163, thanks for your PR! By analyzing the history of the files in this pull request, we identified @benjycui, @waywardmonkeys and @jljsj33 to be potential reviewers.

@afc163 afc163 force-pushed the fix-tooltip-on-disabled-button branch 3 times, most recently from f47ead2 to 6e1a659 Compare February 14, 2017 10:03
@coveralls
Copy link

Coverage Status

Changes Unknown when pulling 6e1a659 on fix-tooltip-on-disabled-button into ** on master**.

@coveralls
Copy link

Coverage Status

Coverage decreased (-0.2%) to 82.086% when pulling 6e1a659 on fix-tooltip-on-disabled-button into e18a330 on master.

@coveralls
Copy link

Coverage Status

Coverage decreased (-0.2%) to 82.086% when pulling 6e1a659 on fix-tooltip-on-disabled-button into e18a330 on master.

@coveralls
Copy link

Coverage Status

Coverage decreased (-0.2%) to 82.086% when pulling 6e1a659 on fix-tooltip-on-disabled-button into e18a330 on master.

@coveralls
Copy link

Coverage Status

Coverage decreased (-0.2%) to 82.086% when pulling 707df13 on fix-tooltip-on-disabled-button into e18a330 on master.

@afc163
Copy link
Member Author

afc163 commented Feb 14, 2017

覆盖率为啥会下降?@yesmeck

@yesmeck
Copy link
Member

yesmeck commented Feb 14, 2017

@ @ 不是很清楚。。因为现在的覆盖率本来就是有点不准的,是按 Babel 转换后的代码计算的,而不是按 TypeScript 计算的。

@afc163 afc163 force-pushed the fix-tooltip-on-disabled-button branch from 707df13 to 449a6a6 Compare February 14, 2017 12:29
@coveralls
Copy link

Coverage Status

Changes Unknown when pulling 449a6a6 on fix-tooltip-on-disabled-button into ** on master**.

@afc163
Copy link
Member Author

afc163 commented Feb 14, 2017

变成 unknown 了...

@coveralls
Copy link

Coverage Status

Coverage decreased (-0.2%) to 82.086% when pulling 774858a on fix-tooltip-on-disabled-button into c296d1a on master.

@afc163 afc163 assigned benjycui and unassigned benjycui Feb 15, 2017
const button = wrapper.find('button').at(0);
button.simulate('mouseenter');
expect(onVisibleChange).not.toHaveBeenCalled();
expect(wrapper.ref('tooltip').prop('visible')).toBe(false);
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

According to me, Tooltip's visible should be true and onVisibleChange should be called when mouse enter button, right?

expect(wrapper.ref('tooltip').prop('visible')).toBe(false);

button.simulate('mouseleave');
expect(onVisibleChange).not.toHaveBeenCalled();
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This should be called, too.

@afc163 afc163 force-pushed the fix-tooltip-on-disabled-button branch from 774858a to adc2068 Compare February 16, 2017 03:47
@coveralls
Copy link

Coverage Status

Coverage decreased (-0.2%) to 82.162% when pulling adc2068 on fix-tooltip-on-disabled-button into 0cb6645 on master.

@afc163
Copy link
Member Author

afc163 commented Jul 27, 2022

#21404 (comment)

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