django-debug-toolbar/debug_toolbar/static, branch restrict-toolbar-handle-to-window A configurable set of panels that display various debug information about the current request/response. toolbar.js: Ensure toolbar handle cannot be dragged outside window 2014-09-14T17:03:11+00:00 Teddy Wing 2014-08-17T01:18:49+00:00 b2957c1782e7053e389d9bb2a3f0f2558a914bfe Previously the toolbar handle could be dragged beyond the top and bottom of the window where it could get lost. If the handle position outside the window border was saved, the only way to get the handle back that I found would be to open the inspector and manually change the handle's offset to make it visible once again. This change restricts the handle so that it cannot be dragged above the top or below the bottom of the window area. Using `event.clientY` in order to get the cursor position relative to the viewport instead of the document (as is the case with `event.pageY`). This allows the handle to be dragged when the page is scrolled. Closes #634. 
Previously the toolbar handle could be dragged beyond the top and bottom
of the window where it could get lost.

If the handle position outside the window border was saved, the only way
to get the handle back that I found would be to open the inspector and
manually change the handle's offset to make it visible once again.

This change restricts the handle so that it cannot be dragged above the
top or below the bottom of the window area.

Using `event.clientY` in order to get the cursor position relative to
the viewport instead of the document (as is the case with
`event.pageY`). This allows the handle to be dragged when the page is
scrolled.

Closes #634.
Remove css text-indent hack for back and close buttons. 2014-08-26T01:37:23+00:00 Bo Lopker 2014-08-26T01:37:23+00:00 69bf1eb127f8c1b6b7c6c2e798ccd208293c1309 Fixes #624. Remove text-index Remove old 'Back' text Remove 'close' text 
Fixes #624.
Remove text-index
Remove old 'Back' text
Remove 'close' text
Keep the toolbar handle pinned to the side after drag event. 2014-07-26T20:25:13+00:00 David Sutherland 2014-07-18T02:28:45+00:00 d177aefdf14be50f24aa376813cd467ee8d4cb18 Current behaviour: after handle is moved when the window width is resized the handled keeps its absolute position rather than sticking to the right side of the window. Handle position returns to normal on page reload. 
Current behaviour: after handle is moved when the window width is resized the handled keeps its absolute position rather than sticking to the right side of the window. Handle position returns to normal on page reload.
Making a basic javascript API for the toolbar. 2014-07-16T01:30:25+00:00 tschilling 2014-07-16T01:30:25+00:00 b80c9221b48784692a7f454ca173c4a267c9f4c0 






Get the relative top rather than the absolute top.
2014-07-05T22:25:18+00:00

tschilling

2014-07-05T22:25:18+00:00

ac539e5ba019a0881b4b28dc2133bcc9f74ce5e3












Prefixing common CSS classes with djdt-
2014-06-18T01:13:24+00:00

tschilling

2014-06-18T01:13:24+00:00

a450969f03449b909716073cfea6898aa56cf54a












Merge pull request #587 from living180/work_around_chrome_mousemove
2014-04-25T16:59:53+00:00

Aymeric Augustin

2014-04-25T16:59:53+00:00

33b8063e1c2bd7349558672df6d5a8f0ed9475b1

Work around spurious mousemove on Chrome.




Work around spurious mousemove on Chrome.






Make the pain go away.
2014-04-25T16:53:00+00:00

Aymeric Augustin

2014-04-25T16:53:00+00:00

727b4e05f59c15904f7b08388220b7bfc76d59b2

Fix #581, #544, #541, #535 and a few others.





Fix #581, #544, #541, #535 and a few others.







Work around spurious mousemove on Chrome.
2014-04-25T15:03:16+00:00

Daniel Harding

2014-04-25T14:58:15+00:00

9bee94d9c00f856be513143927a5299388ee5f59

When clicking on an element in Chrome, spurious mousemove events can be
generated when the cursor hasn't actually moved.  This can prevent the
toolbar from being shown when the handle is clicked because the code
sees the mousemove event and thinks a handle drag is happening.  Work
around this by only running the handle drag code if the cursor has moved
since the mousedown event.





When clicking on an element in Chrome, spurious mousemove events can be
generated when the cursor hasn't actually moved.  This can prevent the
toolbar from being shown when the handle is clicked because the code
sees the mousemove event and thinks a handle drag is happening.  Work
around this by only running the handle drag code if the cursor has moved
since the mousedown event.







Propagate mouseup events when not dragging toolbar
2014-02-25T04:55:23+00:00

David Sutherland

2014-02-25T04:55:23+00:00

decf92eb045a269e69604ef4650d297faceea162

In Chrome (this does not affect Firefox) onchange events on multi-selects are not fired all of the time e.g. with the following template:

<body>
    <select multiple="multiple" onchange="console.log('clicked');">
        <option  value="1">1</option>
    </select>
</body>

Ctrl click on the option and view the js log. many of the events will not register. Therefore stop propagation and prevent default action only when handle is dragged.




In Chrome (this does not affect Firefox) onchange events on multi-selects are not fired all of the time e.g. with the following template:

<body>
    <select multiple="multiple" onchange="console.log('clicked');">
        <option  value="1">1</option>
    </select>
</body>

Ctrl click on the option and view the js log. many of the events will not register. Therefore stop propagation and prevent default action only when handle is dragged.