Closed
Bug 714131
Opened 13 years ago
Closed 12 years ago
[ICS] Implement the new clipboard bar in the actionbar
Categories
(Firefox for Android Graveyard :: General, defect, P2)
Tracking
(firefox11 affected, firefox12 affected, firefox15 verified, blocking-fennec1.0 beta+, fennec11+)
VERIFIED
FIXED
Firefox 13
People
(Reporter: mfinkle, Assigned: sriram)
References
Details
(Keywords: regression, reproducible, uiwanted)
Attachments
(1 file, 1 obsolete file)
6.79 KB,
patch
|
mfinkle
:
review+
|
Details | Diff | Splinter Review |
Steps: 1. Load a website 2. Tap on URLbar to open the awesomescreen 3. long tap on the selected text (the current URL should be selected) The menu that is displayed acts like no text is selected in the textbox. If you pick "Select All", then long tap again and you'll see "Cut" and "Copy" on the menu.
Reporter | ||
Updated•13 years ago
|
Priority: -- → P3
Comment 1•13 years ago
|
||
I don't get a context menu at all in current nightly build, I'm only getting the selection tool.
Comment 2•13 years ago
|
||
(In reply to Martijn Wargers [:mw22] (QA - IRC nick: mw22) from comment #1) > I don't get a context menu at all in current nightly build, I'm only getting > the selection tool. Ditto. Mozilla/5.0 (Android; Linux armv7l; rv:12.0a1) Gecko/20111230 Firefox/12.0a1 Fennec/12.0a1
Comment 3•13 years ago
|
||
Basic feature which is annoying to not have. Recommended P2.
Summary: Context menu in Awesomebar does not act like text is selected → Unable to invoke context menu for any text in the URL Bar
Whiteboard: [QA^]
Updated•13 years ago
|
tracking-fennec: --- → 11+
Comment 4•13 years ago
|
||
http://hg.mozilla.org/mozilla-central/pushloghtml?fromchange=2afd7ae68e8b&tochange=4e4878620bb5 Could be bug 708616, bug 711905, bug 708700 just guessing CC'ing Wes and Sriram.
Keywords: regressionwindow-wanted
Updated•13 years ago
|
Comment 5•13 years ago
|
||
Work around is to switch to landscape keyboard. Also can't select input method without a context menu.
Comment 6•13 years ago
|
||
Apparently this is broken on ICS. This works on a recent inbound build on Gingerbread on my Galaxy SII.
Updated•12 years ago
|
Keywords: reproducible
Whiteboard: [QA^] → [QA^][has-regression-range]
Comment 7•12 years ago
|
||
Also recommending at least P2 - not being able to copy/paste links from other apps/the stock browser into fennec can be quite limiting.
Reporter | ||
Updated•12 years ago
|
Summary: Unable to invoke context menu for any text in the URL Bar → [ICS] Unable to invoke context menu for any text in the URL Bar
Assignee | ||
Comment 8•12 years ago
|
||
In ICS, we might need to add an ActionMode to perform this. Currently we are overriding the ActionBar with our custom ActionBar.
Assignee | ||
Comment 9•12 years ago
|
||
On my further investigation, the edit-text boxes in "ActionBar" have "android:textIsSelectable" to be false. http://developer.android.com/reference/android/widget/TextView.html#attr_android:textIsSelectable [I verified this from logs]. Hence, a new ActionMode would not appear by default. (This happens if the edit-text was available inside the content). I checked apps like People (Contacts app in ICS). The Search box on the ActionBar doesn't allow text selection and pasting. Since ICS doesn't have the ability to have "context menu" on "long press", this feature cannot be triggered by any means. Only way to have the cut, copy, paste is for us to manually have an ActionMode and use it. The stock browser does this differently. To my knowledge, they have their own custom ActionBar. On long press, the contents of the ActionBar is "overlaid" on top of actual screen and shown, and the actual ActionBar moves into an ActionMode showing the icons. Things to note here: 1. The ActionMode for Stock browser (note the "Share" icon to share the URL) uses a custom one. The background color is different as well. 2. The URL bar is either in ActionBar or as part of main layout -- which I couldn't confirm properly. The menu button is confusing me. But Android IRC channel confirmed that they use a custom menu button. If we want edit options, we need to do an ActionMode for our own use.
Updated•12 years ago
|
Whiteboard: [QA^][has-regression-range]
Updated•12 years ago
|
status-firefox13:
--- → affected
Reporter | ||
Updated•12 years ago
|
Keywords: fennecnative-betablocker
Summary: [ICS] Unable to invoke context menu for any text in the URL Bar → [ICS] Implement the new clipboard bar in the actionbar
Assignee | ||
Comment 11•12 years ago
|
||
If we show an ActionMode for these actions, we need to move the ActionBar (currently showing AwesomeBar) to main layout. Is this the desired approach?
Comment 12•12 years ago
|
||
(In reply to Sriram Ramasubramanian [:sriram] from comment #11) > If we show an ActionMode for these actions, we need to move the ActionBar > (currently showing AwesomeBar) to main layout. Is this the desired approach? Performance hit?
Reporter | ||
Updated•12 years ago
|
Assignee: nobody → sriram
Priority: P3 → P2
Updated•12 years ago
|
blocking-fennec1.0: --- → beta+
Updated•12 years ago
|
Status: NEW → ASSIGNED
Assignee | ||
Comment 13•12 years ago
|
||
Playing with ActionMode for some time, I found this. On starting ActionMode on long-press, we need to move the contents of the ActionBar to a temporary View on top of the tabs. The new ActionMode pops up now. However, the text in the EditText (the awesomebar-search) is not selectable! Also, the ActionMode exists from there when I press on the EditText or even when I take my finger from the old EditText. I am unable to fix this part. The other option is to show a "context-menu" with the options. Even then, the select wouldn't be selectable as long as EditText is in ActionBar. This is a known issue in all EditTexts in ICS. e.g. People app.
Comment 14•12 years ago
|
||
Can we play with putting the tabs on top (in the ActionBar) here, and hiding them (the tabs) if the user focuses/starts editing the textbox? That seems more IceCreamSandwichy to me anyway.
Assignee | ||
Comment 15•12 years ago
|
||
This patch brings back the default ActionMode. The ActionBar for AwesomeBar is now removed. This patch adds a small little menu button in Galaxy Nexus. Also, this doesn't address the landscape mode of AwesomeBar -- which wouldn't be needed as the keyboard comes up in landscape mode.
Attachment #605008 -
Flags: review?(mark.finkle)
Reporter | ||
Comment 16•12 years ago
|
||
(In reply to Sriram Ramasubramanian [:sriram] from comment #15) > Created attachment 605008 [details] [diff] [review] > Patch > > This patch brings back the default ActionMode. > The ActionBar for AwesomeBar is now removed. This patch adds a small little > menu button in Galaxy Nexus. We need a way to remove this menu button. How does Chrome and Stock do it? > Also, this doesn't address the landscape mode of AwesomeBar -- which > wouldn't be needed as the keyboard comes up in landscape mode. We are actually working to not use the landscape keyboard. This might not be an issue for long. What impact does it have currently?
Assignee | ||
Comment 17•12 years ago
|
||
The impact in landscape mode is not big. Instead of 42dip height, we will be showing 48dip for AwesomeBar.
Assignee | ||
Comment 18•12 years ago
|
||
This patch avoids the menu button and hides the action-bar in XML (just like TabsTray) -- hence no performance regression. When we long press on the awesomebar-search, the default action-mode kicks in.
Attachment #605008 -
Attachment is obsolete: true
Attachment #605008 -
Flags: review?(mark.finkle)
Attachment #605024 -
Flags: review?(mark.finkle)
Reporter | ||
Updated•12 years ago
|
Attachment #605024 -
Flags: review?(mark.finkle) → review+
Assignee | ||
Comment 19•12 years ago
|
||
http://hg.mozilla.org/integration/mozilla-inbound/rev/f5b002584ce3
Comment 20•12 years ago
|
||
https://hg.mozilla.org/mozilla-central/rev/f5b002584ce3
Status: ASSIGNED → RESOLVED
Closed: 12 years ago
Resolution: --- → FIXED
Target Milestone: --- → Firefox 13
Updated•12 years ago
|
status-firefox13:
affected → ---
Comment 21•12 years ago
|
||
Verified fixed on: Firefox 15.0a1 (2012-05-21) Device: Galaxy Nexus OS: Android 4.0.2
Status: RESOLVED → VERIFIED
status-firefox15:
--- → verified
Updated•3 years ago
|
Product: Firefox for Android → Firefox for Android Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•