Bug #54238
closed
Pagetree pointer cursor broken since ExtJS upgrade
Added by Alexander Stehlik over 10 years ago.
Updated almost 7 years ago.
Description
Since the ExtJS upgrade in f905ff99 the cursor in the pagetree is not displayed as pointer any more (tested in Chrome and Firefox).
Only a very small area between the pagetree elements is displayed as pointer.
This can be a bit confusing for the editors.
This is due to a change in ext-all-notheme.css. See:
https://review.typo3.org/#/c/24883/4/typo3/contrib/extjs/resources/css/ext-all-notheme.css
The pointer was there (and still would be) because of:
.x-tree-node-el {
cursor: pointer;
line-height: 18px;
}
But x-unselectable kicks in now:
.x-unselectable, .x-unselectable * {
...
cursor: default;
}
Vendor-prefixed cursor-definitions for "unselectable" were in place in the past already, just the generic "cursor: default" got added now.
The x-tree-node item remained identical. Only the div got another class added.
Before:
<li class="x-tree-node"><div unselectable="on" class="x-tree-node-el x-tree-node-leaf x-unselectable" ext:tree-node-id="p2" id="extdd-3">
Now:
<li class="x-tree-node"><div unselectable="on" class="x-tree-node-el x-tree-node-leaf x-unselectable x-tree-selected" ext:tree-node-id="p2" id="extdd-3">
Where does the "unselectable" in the tree come from? Is that something we can avoid? Or is it there in our tree on purpose, so we should style this detail in our pagetree with custom-CSS?
- Status changed from New to Under Review
- Status changed from Under Review to Resolved
- % Done changed from 0 to 100
- Status changed from Resolved to Closed
Also available in: Atom
PDF