I think it would be good to split bug 835623 into a new story bug in which case it becomes a 5? and this bug becomes an 8?
Hey Brian, would any of the current dependencies from Bug 845152 move with Bug 835623 if it were to be it's own story?
Hi Asa, with the removal of the work item 835623, does the existing story for 845152 require modification?
> for 845152 require modification?
Nope. This story is still fine.
I'll own this story. Jonathan and I are working on its two remaining work bugs.
Thanks Frank.  I'll include it as part of IT#10.
This bug has increased in difficulty and scope since we last estimated its LOE, due to the update of design specs and inclusion of the half-height autocomplete.
Could you raise this to a p=20? Jonathan's piece alone would at least account for p=13.
Hi Frank.  Thanks for the update.  Yes, I'll increase the point estimate for this feature story to 20.
Adding updated wallpaper patch to Bug 891656 for Iteration #13.
If I'm not mistaken, all of the stuff we were planning to do for the preview for this bug has been completed. Should I go ahead and close?
No, Asa is evaluating the final bug.  He's going to provide a recommendation early next week.
I'm hopeful that we're good enough here but I want to look at this across a range of devices and make sure there's nothing ugly left with the clipping issue. Once the bandaid is verified sufficient, we'll close out this story.
I think we can close this story but we have to keep one remaining defect open on a couple of buttons being right-side clipped in high-dpi mode that I think we must fix before release. That being said, the story here is functional. We have everything we want except this one visual glitch.
Marking as Resolved based on Asa's Comment #14 and leaving Bug 905453 as an MP Defect.
Verified as fixed while testing for iteration #17, with latest Nightly (build ID: 20131028030205) on Win 8-32bit, following the user story from comment 0.I can see round and complete icons for all buttons, with no cut offs.