Just to clarify the intent of this bug. We're tracking the minimal feature set needed to land Facebook sharing by the cut off date, currently May 24th. This probably means the following feature set, likely in this order: * Sharing on your wall ** Editing share title ** Editing share description ** Choosing an image or not (stop showing thumbnail view) * Choosing the post privacy level * Choosing from a set of images * Posting to a friends wall * Posting to a group wall
Summary: [meta] facebook ui tracking → [meta] facebook ui tracking (minimal set needed to land)
(In reply to comment #1) > Just to clarify the intent of this bug. We're tracking the minimal feature > set needed to land Facebook sharing by the cut off date, currently May 24th. > > > This probably means the following feature set, likely in this order: > * Sharing on your wall > ** Editing share title > ** Editing share description > ** Choosing an image or not (stop showing thumbnail view) > * Choosing the post privacy level > * Choosing from a set of images > * Posting to a friends wall > * Posting to a group wall Some ideas for how to include these things into the revised panel UI: Left Side (v01): - Separates webpage content (title, link, summary) into its own area - Visually separate from your message - Denotes editable parts with pencil icon Right Side (v02): - Puts all editable content into fields - No visual separation - Includes attempt at thumbnail management Thumbnail micromanagement almost seem like overkill to me. Initially at least.
Component: Share: Web Client → F1
Product: Mozilla Services → Mozilla Labs
QA Contact: share-web-client → f1
How "final" is this design? There are a couple issues that are nontrivial to overcome. I'm not really looking at the facebook part, but rather the "tab" management and the gradients. 1. The difference between this panel design and the standard firefox panels on non-osx platforms (ie. the panel design is closest to osx). The second is the left pointing arrow. Will we have designs for non-osx that match the platforms chrome? 2. Since the main content area has gradation of color, using an image for that arrow is painful as it would require multiple images to match the gradient at different heights. Doing this with CSS is proving equally hard due to the gradient. If the main content area were a solid color, this would be trivial (I have css that works wonderfully for that). For now, I am going to leave out the left pointing arrow.
saving this hear to remind me what i did to get a css based arrow indicator for the tab
f1 is no longer an active project. delete these messages by searching for: [closing_f1_project_bugs]
Status: NEW → RESOLVED
Last Resolved: 6 years ago
Resolution: --- → INVALID
You need to log in before you can comment on or make changes to this bug.