Bug #24004
closed
navFrameWidth and navFrameResizable are not respected any more
0%
Description
After changing the complete backend to extjs viewports and removing the framesets, navFrameWidth and navFrameResizable are not respected any more.
Setting these does not have an effect.
While the first one needs to be fixed, the second one can be deprecated, as it's not needed any more.
Idea how to fix this by Steffen Gebert:
"Hopefully we get a StateProvider, which saves the state in the BE_USER uc field. SteffenK's ExtDirect provider for the User Settings is the foundation for this. I think the remainder is pretty easy then. This will save the state of the panels (width, collapsed etc)"
(issue imported from #M16331)
Updated by Steffen Gebert over 13 years ago
navFrameResizable makes no sense anymore, as we can resize AND collapse WITHOUT any option.. isn't this fantastic?? kidding
The StateProvider is in place (you see the ExtDirect call, after resizing the frame?). However the state seems not the be reflected, when the backend is reloaded.
Would be a task for SteffenK
Updated by Steffen Gebert over 13 years ago
Technical part in #24592, I keep this open to notify the Documentation Team about the removal.
Updated by Christian Kuhn over 13 years ago
@Steffen: If both settings are not valid anymore: Why not just add a wiki entry to 'pending documentation' to remove those two, refer to this issue and close it?
Updated by Steffen Gebert over 13 years ago
Yes, thanks for kicking my ass - was just too lazy ;-)
However, as we want Docs ready for the release, I took the 2min to look up the section and add the comment.
Updated by