Skip to content

Conversation

@07ARB
Copy link
Contributor

@07ARB 07ARB commented Oct 25, 2019

What changes were proposed in this pull request?

All tooltips message will display in centre.

Why are the changes needed?

Some time tooltips will hide the data of column and tooltips display position will be inconsistent in UI.

Does this PR introduce any user-facing change?

yes.

Screenshot 2019-10-26 at 3 08 51 AM

How was this patch tested?

Manual test.

…te,Blacklisted,Logs,Threaddump columns

    ### What changes were proposed in this pull request?
    All tooltips message will display in center.

    ### Why are the changes needed?
    Some time tooltips will hide the data of column and tooltips display position will be inconsistent in UI.

    ### Does this PR introduce any user-facing change?
    yes.

    ### How was this patch tested?
    Manual test.

    Authored-by: Ankit Raj Boudh <ankitrajboudh@gmail.com>
@07ARB
Copy link
Contributor Author

07ARB commented Oct 27, 2019

@srowen please help me to review this PR

@srowen
Copy link
Member

srowen commented Oct 27, 2019

How about we standardize on "auto" everywhere? is that the default? It's good to standardize but I think we can let the browser decide, as the right placement will depend on where the elements show in the window.

@07ARB
Copy link
Contributor Author

07ARB commented Oct 28, 2019

I think that's also fine, I will change to auto.

07ARB added 10 commits October 29, 2019 02:51
Fixed review comments given by srowen,changed data-placement from top to auto.
Fixed review comments given by srowen,changed data-placement from top to auto.
Fixed review comments given by srowen,changed data-placement from top to auto.
Fixed review comments given by srowen,changed data-placement from top to auto.
Fixed review comments given by srowen,changed data-placement from top to auto.
Fixed review comments given by srowen,changed data-placement from top to auto.
Fixed review comments given by srowen,changed data-placement from top to auto.
Fixed review comments given by srowen,changed data-placement from top to auto.
Fixed review comments given by srowen,changed data-placement from top to auto.
Fixed review comments given by srowen,changed data-placement from top to auto.
@07ARB
Copy link
Contributor Author

07ARB commented Oct 29, 2019

@srowen, I have fixed the review comments,please check.

Copy link
Member

@srowen srowen left a comment

Choose a reason for hiding this comment

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

Are these all the data-placement occurrences?

val headerSpan = tooltip.map { case (title, left) =>
if (left) {
/* Place the shuffle write tooltip on the left (rather than the default position
/* Place the shuffle write tooltip on the auto (rather than the default position
Copy link
Member

Choose a reason for hiding this comment

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

Nit: we need to reword this comment: "Place the tooltip automatically rather than on top because..."
Actually you don't need the if-else here anymore?
It might be worth double-checking that the auto placement on this element works well.

Copy link
Member

Choose a reason for hiding this comment

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

@07ARB I think we can make one more change here to simplify.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

@srowen, auto is not working properly ,tooltips will display always in top-left corner of browser (chrome).
Screenshot 2019-11-06 at 8 22 32 AM

Copy link
Member

Choose a reason for hiding this comment

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

That's weird! OK then let's standardize on anything that displays reasonably everywhere. I think a few of these worked differently on purpose to avoid display issues though; maybe we leave any special logic as-is.

07ARB added 4 commits November 7, 2019 03:27
…te,Blacklisted,Logs,Threaddump columns

    ### What changes were proposed in this pull request?
    All tooltips message will display in center.

    ### Why are the changes needed?
    Some time tooltips will hide the data of column and tooltips display position will be inconsistent in UI.

    ### Does this PR introduce any user-facing change?
    yes.

    ### How was this patch tested?
    Manual test.

    Authored-by: Ankit Raj Boudh
@07ARB 07ARB requested a review from srowen November 6, 2019 23:15
Copy link
Member

@srowen srowen left a comment

Choose a reason for hiding this comment

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

Generally I'm just wondering if it results in tooltip placement that is not worse in all cases. Standardization is good; in some cases a different placement might still be needed.

the tooltip is wider than the column, so it doesn't fit on top. */
<span data-toggle="tooltip" data-placement="left" title={title}>
val headerSpan = if (null != tooltip && !tooltip.isEmpty) {
<span data-toggle="tooltip" data-placement="top" title={tooltip}>
Copy link
Member

Choose a reason for hiding this comment

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

This is an example of a case where the placement appears to be on purpose. How does this look before and after?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

ok i will give you the screenshot

Copy link
Contributor Author

@07ARB 07ARB Nov 6, 2019

Choose a reason for hiding this comment

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

Before :
Screenshot 2019-11-08 at 12 16 11 AM

After my Change :
Screenshot 2019-11-07 at 10 01 34 PM

Copy link
Contributor Author

@07ARB 07ARB Nov 8, 2019

Choose a reason for hiding this comment

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

@srowen , please check this if you still feel it's not require then we can close this PR.

@07ARB 07ARB requested a review from srowen November 8, 2019 04:47
@AbhishekNew
Copy link

Display tooltip at center is standard. Looks good to me.

@SparkQA
Copy link

SparkQA commented Nov 9, 2019

Test build #4917 has finished for PR 26263 at commit 1a75e4d.

  • This patch fails Spark unit tests.
  • This patch does not merge cleanly.
  • This patch adds no public classes.

@SparkQA
Copy link

SparkQA commented Nov 10, 2019

Test build #4918 has finished for PR 26263 at commit 1a75e4d.

  • This patch fails Spark unit tests.
  • This patch does not merge cleanly.
  • This patch adds no public classes.

@07ARB
Copy link
Contributor Author

07ARB commented Nov 11, 2019

Failure test cases not related to this PR.

@SparkQA
Copy link

SparkQA commented Nov 11, 2019

Test build #4922 has finished for PR 26263 at commit 1a75e4d.

  • This patch fails Spark unit tests.
  • This patch merges cleanly.
  • This patch adds no public classes.

@SparkQA
Copy link

SparkQA commented Nov 11, 2019

Test build #4923 has finished for PR 26263 at commit 1a75e4d.

  • This patch passes all tests.
  • This patch merges cleanly.
  • This patch adds no public classes.

@SparkQA
Copy link

SparkQA commented Nov 11, 2019

Test build #4927 has finished for PR 26263 at commit 1a75e4d.

  • This patch passes all tests.
  • This patch merges cleanly.
  • This patch adds no public classes.

@SparkQA
Copy link

SparkQA commented Nov 11, 2019

Test build #4926 has finished for PR 26263 at commit 1a75e4d.

  • This patch passes all tests.
  • This patch merges cleanly.
  • This patch adds no public classes.

@srowen srowen closed this in 45e212e Nov 13, 2019
@srowen
Copy link
Member

srowen commented Nov 13, 2019

Merged to master

@07ARB
Copy link
Contributor Author

07ARB commented Nov 13, 2019

@srowen , Thank you for your guidance and i really feel good working with you.

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

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants