Skip to content
This repository has been archived by the owner on Jan 11, 2023. It is now read-only.

[Preview] 'Split console' overlays the debugger variable tooltip #5134

Closed
jnachtigall opened this issue Jan 18, 2018 · 14 comments
Closed

[Preview] 'Split console' overlays the debugger variable tooltip #5134

jnachtigall opened this issue Jan 18, 2018 · 14 comments
Assignees
Milestone

Comments

@jnachtigall
Copy link
Contributor

STR:

  1. Set a breakpoint and also enable Toggle split console [esc])
  2. Hover a variable at bottom

AR:
The variable tooltip is cropped:
image

ER:
Don't crop. Either have the tooltip above the Split console. Or: Take the opened console into consideration while calculation into which direction the tooltop should open (So in this case not to the bottom but to the top).

@claim claim bot added the not-available label Jan 18, 2018
@lukaszsobek lukaszsobek changed the title 'Split console' overlays the debugger variable tooltip [UI] 'Split console' overlays the debugger variable tooltip Jan 21, 2018
@lukaszsobek
Copy link
Contributor

Thinking about it there seem to be two situations worth considering:
1.) the debugger is too low to hold the tooltip.
2.) the debugger is too narrow to hold the tooltip.

What would you say should happen in such situations?

@jasonLaster
Copy link
Contributor

@juliandescottes do you think we could use a XUL wrapper here?

@jnachtigall
Copy link
Contributor Author

What would you say should happen in such situations?

From a user perspective I would expect the tooltip to overlay just like normal, that is, with part of it overlaying over the normal html content (and not be confined to the debugger window). Don't know if this is technically possible though, because afaik the debugger is in its own iframe or so. (But at least this might be possible with regards to the Console split area)

@juliandescottes
Copy link
Member

XUL is on the way out, we shouldn't invest in this direction. We should design tooltips to fit in the devtools frame.

Regardless of XUL, the DevTools tooltip is creating tooltip containers in the topmost devtools frame, so even without XUL we have no overlapping issues between devtools panels (eg splitconsole, devtools toolbar etc). It also takes care of calculating best position for the tooltip.

I would be concerned with having the debugger relying on a different tooltip implementation on github vs mc. Given the current workflow I think I'd prefer the debugger to keep a custom implementation, even if it's more limited.

Calculate the available space in the debugger frame and anchor the tooltip accordingly.

@ochameau
Copy link
Contributor

@bgrins is there any plan to replace xul:popup/xul:panel with something else? If not a plan, has it been discussed? I find it quite frustrating to limit devtools UX because of XUL being deprecated.

@jasonLaster jasonLaster changed the title [UI] 'Split console' overlays the debugger variable tooltip [Preview] 'Split console' overlays the debugger variable tooltip Feb 13, 2018
@tripurari001
Copy link
Contributor

I would like to work on this

My approach would be to calculate the best position to open the tool-tip ( top or bottom ) based on the position of element ( hovered one )

@tripurari001
Copy link
Contributor

/claim

@claim
Copy link

claim bot commented Feb 13, 2018

Thanks for claiming the issue! 👋

Here are some links for getting setup, contributing, and developing. We're always happy to answer questions in slack! If you become busy, feel free to /unclaim it.

🦊 Debugger team!

@darkwing
Copy link
Contributor

Great @tripurari001 ! Let us know if we can help along the way :)

@tripurari001
Copy link
Contributor

sure @darkwing , Thanks

@jasonLaster
Copy link
Contributor

Hey, @tripurari001, I'm un-assigning you as it's been a month. Feel free to re-claim it if you have time

@jbhoosreddy
Copy link
Contributor

Been trying to reproduce this issue.

  1. update to master. 2. ./bin/download-firefox-artifact. 3. yarn copy-assets-watch

    The split console is not over the popup.

@jasonLaster
Copy link
Contributor

yep! that is true

@jasonLaster
Copy link
Contributor

Hmm, it looks like we try to avoid it, but expanding a node causes it

@jbhoosreddy jbhoosreddy assigned darkwing and unassigned jbhoosreddy Jun 23, 2018
@jasonLaster jasonLaster modified the milestones: May 8th, June 26 Jun 26, 2018
@darkwing darkwing modified the milestones: June 26, July 17th Jul 10, 2018
@jasonLaster jasonLaster modified the milestones: July 17th, July 31st Jul 17, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

8 participants