Opened 3 years ago
Closed 3 years ago
#13220 closed defect (bug) (fixed)
Nav Menus 3.0 Code Sprint
| Reported by: |
|
Owned by: |
|
|---|---|---|---|
| Priority: | normal | Milestone: | 3.0 |
| Component: | Menus | Version: | 3.0 |
| Severity: | normal | Keywords: | |
| Cc: |
Description
Working ticket for the nav menus 3.0 code sprint.
Attachments (30)
Change History (54)
comment:1
ptahdunbar — 3 years ago
- Milestone changed from Unassigned to 3.0
- Version set to 3.0
ptahdunbar — 3 years ago
comment:3
follow-up:
↓ 4
markmcwilliams — 3 years ago
The UI changes are looking much better, I just have 1 concern over the amount of white space found on the right-hand side, it's like it's making room for another column or something? If you take a look at http://twitpic.com/1kgrlr then the bit in red shows you exactly, would it make sense to have that fill the space available?
In my opinion, yes I think it would!
Replying to markmcwilliams:
The UI changes are looking much better, I just have 1 concern over the amount of white space found on the right-hand side, it's like it's making room for another column or something? If you take a look at http://twitpic.com/1kgrlr then the bit in red shows you exactly, would it make sense to have that fill the space available?
In my opinion, yes I think it would!
Having the menu items as fixed width makes sense because it means that the input boxes aren't stretched out or look too short within the box (like they would be if the item box was full width). It probably also gives a little bit more distinction to the nested items as well.
Nesting and not breaking out of the container upon expansion are the reasons behind the whitespace, as suggested above.
koopersmith — 3 years ago
koopersmith — 3 years ago
koopersmith — 3 years ago
koopersmith — 3 years ago
koopersmith — 3 years ago
koopersmith — 3 years ago
koopersmith — 3 years ago
- Priority changed from normal to high
- Type changed from enhancement to defect (bug)
i`m not really sure if it depends on one of these updates today but i thinke one of the javascript updates broke the editor (javascripts) and some more stuff in the dashboard.. (?)
sorry if i`m wrong - but everything (trunk) was working nice till one update (about js) today
- Priority changed from high to normal
Replying to LazyMe:
i`m not really sure if it depends on one of these updates today but i thinke one of the javascript updates broke the editor (javascripts) and some more stuff in the dashboard.. (?)
sorry if i`m wrong - but everything (trunk) was working nice till one update (about js) today
define ('CONCATENATE_SCRIPTS', false);
if false, it works again - if true it depends on the blog.. strange. (since today - trunk)
comment:10
follow-up:
↓ 13
nacin — 3 years ago
define(SCRIPT_DEBUG, true) loads unconcatenated scripts and also the development versions. We didn't bump the script loader every single commit yesterday, so you may need to bust your cache.
comment:11
in reply to:
↑ 5
markmcwilliams — 3 years ago
Replying to jane:
Nesting and not breaking out of the container upon expansion are the reasons behind the whitespace, as suggested above.
Fair enough! :)
comment:12
ocean90 — 3 years ago
@LazyMe
Thanks, it's fixed in #9008
comment:13
in reply to:
↑ 10
LazyMe — 3 years ago
Replying to nacin:
define(SCRIPT_DEBUG, true) loads unconcatenated scripts and also the development versions. We didn't bump the script loader every single commit yesterday, so you may need to bust your cache.
i`m stupid - thanks for the information, nacin.
comment:14
nacin — 3 years ago
It actually was a bug of some sort, see #9008.
ptahdunbar — 3 years ago
ptahdunbar — 3 years ago
ptahdunbar — 3 years ago
ptahdunbar — 3 years ago
ptahdunbar — 3 years ago
comment:15
nacin — 3 years ago
koopersmith — 3 years ago
comment:16
nacin — 3 years ago
koopersmith — 3 years ago
comment:17
koopersmith — 3 years ago
Missed a variable in js.warnings.begone.1.patch, was causing a bug in select all. Fixed above.
koopersmith — 3 years ago
comment:18
nacin — 3 years ago
koopersmith — 3 years ago
koopersmith — 3 years ago
comment:19
nacin — 3 years ago
comment:20
nacin — 3 years ago
koopersmith — 3 years ago
koopersmith — 3 years ago
koopersmith — 3 years ago
comment:21
nacin — 3 years ago
comment:22
ocean90 — 3 years ago
See #13311
Another thing: http://grab.by/4hLW If a post/page has no title we should add (no title) as menu label
koopersmith — 3 years ago
comment:23
nacin — 3 years ago
comment:24
ryan — 3 years ago
- Resolution set to fixed
- Status changed from new to closed

changes "text" to "label" for the custom links metabox. corrects the alignment for list-controls links