Page Action extension dev strategies
Reported by
pushkar.aditya@gmail.com,
Aug 21 2016
|
||
Issue descriptionUserAgent: Mozilla/5.0 (Windows NT 6.1; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/52.0.2743.116 Safari/537.36 Steps to reproduce the problem: I am new to chrome extension development and I am not sure if this is the right forum for posting my dis-content about developing the chrome extension. In case it is not the right forum, please help me to navigate to right one. I am bit frustrated to find out the process of enabling and disabling the page action icon for chrome extension. Sending a message to background page/script and then showing the icon makes it two step process, nonetheless it is confusing for beginners. In my opinion, control for enabling the icon (which in turns controls enabling/disabling of extension) is always with control script which logically make much sense rather than giving to background script (please understand I am not talking here about implementation perspective but business or logical perspective). In my support, I have found many questions (some having confusing answers) which support my conclusion. Also, I got to know that page actions has been moved out of omnibox which was unprecedented for me. I personally would like to see them back in, similar to bookmark, password or language translation functionality. What is the expected behavior? What went wrong? N/A WebStore page: Did this work before? N/A Chrome version: 52.0.2743.116 Channel: stable OS Version: 6.1 (Windows 7, Windows Server 2008 R2) Flash Version: Shockwave Flash 22.0 r0
,
Aug 22 2017
Issue has not been modified or commented on in the last 365 days, please re-open or file a new bug if this is still an issue. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot |
||
►
Sign in to add a comment |
||
Comment 1 by ranjitkan@chromium.org
, Aug 22 2016