Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

tab when resources panel is closed is too small #9093

Closed
xxxmicrobexxx opened this issue Nov 12, 2012 · 3 comments
Closed

tab when resources panel is closed is too small #9093

xxxmicrobexxx opened this issue Nov 12, 2012 · 3 comments
Labels
bug The issue in the code or project, which should be addressed. type-frontend Issues related to UI/UX issues, mostly about styles and frontend implementations on JavaScript.

Comments

@xxxmicrobexxx
Copy link

xxxmicrobexxx created Redmine issue ID 9093

When the resources/elements/files panel is closed, the tab is just too small to be obvious for people who aren't aware of why their resources panel is missing.

Make it longer, make it wider. Please go for useability over styling that frustrates.

@exside
Copy link
Contributor

exside commented Apr 4, 2013

exside submitted:

Fix ready on gitHub, could be in 2.2.7 =)

@opengeek
Copy link
Member

opengeek commented Apr 4, 2013

opengeek submitted:

cherry-picked into release-2.2 for inclusion in 2.2.7

see 130c273

@exside
Copy link
Contributor

exside commented Apr 4, 2013

exside submitted:

great work! Kudos to you and romain (and the other contributors!)! Really working hard! Will be a great release!!!

enigmatic-user pushed a commit to enigmatic-user/revolution that referenced this issue Feb 13, 2014
[9093] - See http://tracker.modx.com/issues/9093
Instead of making the split region wider, i tried to make it more "visible".
(cherry picked from commit cb18d20)
enigmatic-user pushed a commit to enigmatic-user/revolution that referenced this issue Feb 13, 2014
enigmatic-user pushed a commit to enigmatic-user/revolution that referenced this issue Feb 13, 2014
Merge branch 'release-2.2'

* release-2.2: (131 commits)
  Bump version for 2.2.7-pl
  Bump version for real 2.2.7-pl release
  Revert [#6271] Limit reserved class_key column...
  Bump version for 2.2.7-pl release
  [#6271] Limit reserved class_key column to inherit="single"
  System Setting update processor E_NOTICE errors
  Allow unpublished in modContext::getResourceURI()
  Minor correction of Czech lexicon
  Update of Czech localization for 2.2.7
  [#9793] Preserve keys in xPDOObject::getMany()
  [modxcms#9773] Fix classKey errors viewing manager actions
  Bump version for 2.2.7-dev
  Minor updates to the Dutch lexicon
  PHPDoc…
  [9774] - See http://tracker.modx.com/issues/9774 Make sure we can not unpublish a 'site_start' resource via tree contextual menu
  Update copyright dates
  italian lexicon update
  [modxcms#9093] Use dark grey vs green for collapse tab
  [modxcms#8138] add changelog entry
  [9237] - See http://tracker.modx.com/issues/9237 Make sure modContextSetting object are given in the create/update processor responses
  ...
pixelchutes pushed a commit to pixelchutes/revolution that referenced this issue Mar 1, 2014
* release-2.2: (48 commits)
  Bump version for 2.2.7-pl
  Bump version for real 2.2.7-pl release
  Revert [#6271] Limit reserved class_key column...
  Bump version for 2.2.7-pl release
  [#6271] Limit reserved class_key column to inherit="single"
  System Setting update processor E_NOTICE errors
  Allow unpublished in modContext::getResourceURI()
  Minor correction of Czech lexicon
  Update of Czech localization for 2.2.7
  [#9793] Preserve keys in xPDOObject::getMany()
  [modxcms#9773] Fix classKey errors viewing manager actions
  Bump version for 2.2.7-dev
  Minor updates to the Dutch lexicon
  PHPDoc…
  [9774] - See http://tracker.modx.com/issues/9774 Make sure we can not unpublish a 'site_start' resource via tree contextual menu
  Update copyright dates
  italian lexicon update
  [modxcms#9093] Use dark grey vs green for collapse tab
  [modxcms#8138] add changelog entry
  [9237] - See http://tracker.modx.com/issues/9237 Make sure modContextSetting object are given in the create/update processor responses
  ...

Conflicts:
	_build/build.sample.properties
	_build/build.xml
	core/docs/changelog.txt
	core/docs/version.inc.php
	core/model/modx/processors/resource/gettoolbar.class.php
This issue was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug The issue in the code or project, which should be addressed. type-frontend Issues related to UI/UX issues, mostly about styles and frontend implementations on JavaScript.
Projects
None yet
Development

No branches or pull requests

3 participants