[chromium-dev] Re: Extensions and the Mac
Don't forget x64 user... ;)
On Dec 10, 7:03 pm, Avi Drissman wrote:
> "plugins": {
> "mac": ...
> "win": ...
> "linux": ...
> }
--
Chromium Developers mailing list: chromium-dev@googlegroups.com
View archives, change email options, or unsubscribe:
http://groups.google.com/group/chromium-dev
[chromium-dev] Chrome Market share overpass 2% for the first time!
Congratulation to the Chrome/Chromium team. For the first time, the market share of Chrome have hit 2.03% on Saturday et 2.05% on Sunday on Net Application. http://marketshare.hitslink.com/google-chrome-market-share.aspx?sample=27&qprid=32&qpcustom=Chrome&qpsp=3531&qpnp=270&qptimeframe=D Congratulation! --~--~-~--~~~---~--~~ Chromium Developers mailing list: chromium-dev@googlegroups.com View archives, change email options, or unsubscribe: http://groups.google.com/group/chromium-dev -~--~~~~--~~--~--~---
[chromium-dev] Re: how to hide navigate bar
Make your url an application.
On Jan 13, 12:41 am, if-ifone wrote:
> it is known that popup browser with maxsize and no navigate bar can use
> script like below
>
> window.open('test.html','blank','fullscreen=1,toolbar=no,menubar=no,scrollb
> ars=no,resizable=yes,location=no,status=no');
> how ever chrome always show white location bar like attach shows.
> how to hide it.
>
> thanks
>
> --
> thinking
>
> navigate.JPG
> 3KViewDownload
--~--~-~--~~~---~--~~
Chromium Developers mailing list: chromium-dev@googlegroups.com
View archives, change email options, or unsubscribe:
http://groups.google.com/group/chromium-dev
-~--~~~~--~~--~--~---
[chromium-dev] Re: Trunk build's biggest annoyances?
There is one more annoyance that I will like to see fixed: Inspected nodes no longer highlighted in the inspector http://code.google.com/p/chromium/issues/detail?id=5178 On Dec 15, 7:50 pm, "Mark Larson (Google)" wrote: > public on chromium-dev.> > I want to do a Dev channel release from the trunk soon. > > I know there are a lot of issues with the current trunk because it hasn't > had the same test exposure or release pressure as the 154 branch. > > I don't plan to get trunk to a Beta level of stability before releasing, but > I would like to know what the biggest problems are so we can evaluate what > needs to be fixed (or put under 'Known Issues'). I know there are bugs on > file, but I'm trying to get a sense of the real burning issues from people > who are actually using trunk (or trying to use it) every day. > > So... what are the 1-3 top issues you think need to get fixed on trunk to > make it bearable for everyday use? > > My biggest peeve right now is the browser crash when you close an app window > (at least once a day I take down my whole browser by closing my calendar. > D'oh!). > > --Mark --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "Chromium-dev" group. To post to this group, send email to chromium-dev@googlegroups.com To unsubscribe from this group, send email to chromium-dev+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/chromium-dev?hl=en -~--~~~~--~~--~--~---
[chromium-dev] Re: Design for better supporting bookmarklets
Just some random idea of other possibility. This random idea is that when you move your mouse over the star, a circle show up with all possibilities for the given web site. Also, if you click the star, it will just bookmark as normal. One thing forever that I will have like to be able to do will have been to replace the star with a very small summary of which icon are available. Like if we put ssl icon in this circle, the user will probably want to see the ssl icon without having to go over the star just as for rss feed detector. http://i41.tinypic.com/2en0vuf.png On Dec 16, 8:33 pm, Nick Baum wrote: > Hi all, > > I've posted a document that describes how we could better support > bookmarklets: > > http://sites.google.com/a/chromium.org/dev/user-experience/bookmarklets > > Let me know if you have any feedback! > Cheers, > > -Nick --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "Chromium-dev" group. To post to this group, send email to chromium-dev@googlegroups.com To unsubscribe from this group, send email to chromium-dev+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/chromium-dev?hl=en -~--~~~~--~~--~--~---
[chromium-dev] Re: Trunk build's biggest annoyances?
Here is one: when you have a window without tab, just a caption and a icon, the icon doesn't show as a button. :) On Dec 16, 2:56 am, Adam Barth wrote: > Apparently my bug searching skills just suck. :) > > > > On Mon, Dec 15, 2008 at 11:52 PM, Adam Barth wrote: > > I'm not sure what the policy is for making up labels on the bug > > tracker, but I labeled these bugs "SuperAnnoying". I filed and > > labeled another bug (space bar doesn't scroll window). > > > Either my bug search skills suck or not that many people are > > dogfooding trunk. How can it be that no one noticed that the space > > bar doesn't scroll the page or that the Facebook home screen is > > rendered wrong? (Maybe these are very recent regressions?) > > > Adam > > > On Mon, Dec 15, 2008 at 5:01 PM, Patrick Johnson > > wrote: > > >> I thinkhttp://crbug.com/5118is one of my biggest annoyances. I'm a > >> fan of tab dragging, and it's been fairly broken recently (at least in > >> maximized mode). > > >> Patrick > > >> On Mon, Dec 15, 2008 at 4:50 PM, Mark Larson (Google) > >> wrote: > >>> >>> public on chromium-dev.> > >>> I want to do a Dev channel release from the trunk soon. > >>> I know there are a lot of issues with the current trunk because it hasn't > >>> had the same test exposure or release pressure as the 154 branch. > >>> I don't plan to get trunk to a Beta level of stability before releasing, > >>> but > >>> I would like to know what the biggest problems are so we can evaluate what > >>> needs to be fixed (or put under 'Known Issues'). I know there are bugs on > >>> file, but I'm trying to get a sense of the real burning issues from people > >>> who are actually using trunk (or trying to use it) every day. > >>> So... what are the 1-3 top issues you think need to get fixed on trunk to > >>> make it bearable for everyday use? > >>> My biggest peeve right now is the browser crash when you close an app > >>> window > >>> (at least once a day I take down my whole browser by closing my calendar. > >>> D'oh!). > >>> --Mark --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "Chromium-dev" group. To post to this group, send email to chromium-dev@googlegroups.com To unsubscribe from this group, send email to chromium-dev+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/chromium-dev?hl=en -~--~~~~--~~--~--~---
[chromium-dev] Re: What's missing in my view?
I wanted to reply earlier, but i got some problem with my build :( Anyway, your problem is that your label is rendered behind the tab content. To test that behavior, try to reduce the height of the tabcontent and put your label right under it, it should now display your text. There is no way to fix the problem that your label is rendered behind the tab content, because there is no system in that allow you to change the display order right now in chrome. But I will suggest you to look at StatusBubble, you mind find what you are searching for over there to implement the resize corner. Jo On Dec 12, 4:32 pm, Marc-Andre Decoste wrote: > Salut, > > I'm working on the resize corner view and am having a little trouble > getting it to work. I tried to use the sample code provided > inhttp://dev.chromium.org/developers/design-documents/views-windowing, by > doing as follows: > > - in BrowserView::Init(), I create a label view and add it as a child of > the contents_container_ > - in BrowserView::Layout(), I get the parent of the label, as well as the > preferred size of the label and then do as follows: > label->SetBounds((parent_view->width() - ps.width() )/ 2, > (parent_view->height() - ps.height()) / 2, > ps.width(), ps.height()); > - Then I run with a break point in Label::Paint() and it seems to do as > it is told except... > I don't see the Hello World text drawn anywhere... > - I also tried my own BrowserResizerView class which also has mouse event > overrides and they never get called, only the Paint override which seems to > be painting on a /dev/nul canvas... > > What am I doing wrong? Do we have more detailed documentation about this, > or ishttp://dev.chromium.org/developers/design-documents/chromeviewsthe > only source of info we currently have? > > Thanks! > > BYE > MAD --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "Chromium-dev" group. To post to this group, send email to chromium-dev@googlegroups.com To unsubscribe from this group, send email to chromium-dev+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/chromium-dev?hl=en -~--~~~~--~~--~--~---
[chromium-dev] Re: data resources and localized strings on linux
Fast question, have you think about adding checksum? On Dec 8, 12:15 pm, [EMAIL PROTECTED] wrote: > I wrote a short design doc about handling data resources and localized > strings on linux. > > http://sites.google.com/a/chromium.org/dev/developers/design-document... > > Feedback welcome. > > tony --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "Chromium-dev" group. To post to this group, send email to chromium-dev@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/chromium-dev?hl=en -~--~~~~--~~--~--~---
[chromium-dev] V8Bindings_prebuild compile error @rev 5247
On the latest revision @5254, I got those errors: 1>-- Build started: Project: V8Bindings_prebuild, Configuration: Release Win32 -- 1>Performing Custom Build Step 1>..\..\..\third_party\WebKit\WebCore\bindings\js\PausedTimeouts.h 1>1 File(s) copied 1>..\..\..\third_party\WebKit\WebCore\bindings\js\PausedTimeouts.cpp 1>1 File(s) copied 1>C:\Users\Admin\Desktop\Chromium\src\chrome\Release\obj\V8Bindings \DerivedSources 1>Building DerivedSources /cygdrive/c/Users/Admin/Desktop/Chromium/src/ webkit/port... 1>[ERROR] Can't open directory /cygdrive/c/Users/Admin/Desktop/ Chromium/src/THIRD_~1/WebKit/WebCore/../../../webkit/port/xml: "No such file or directory" 1>[ERROR] Can't open directory /cygdrive/c/Users/Admin/Desktop/ Chromium/src/THIRD_~1/WebKit/WebCore/../../../webkit/port/xml: "No such file or directory" 1>[ERROR] Can't open directory /cygdrive/c/Users/Admin/Desktop/ Chromium/src/THIRD_~1/WebKit/WebCore/../../../webkit/port/xml: "No such file or directory" . . . After some investigation, it seen that it is related with the revision 5247 which deleted two directory: trunk/src/webkit/port/page/win/ trunk/src/webkit/port/xml/ darin, did you forgot to send an updated version of trunk/src/webkit/ port/DerivedSources.make @rev 5247 ? Or I missed something? Because still I don't get why it compile on the buildbot... Also, in revision 5203, the directory port/ksvg2 and port/svg got deleted, but nobody updated DerivedSources.make. I merged the required change in this patch: Index: DerivedSources.make === --- DerivedSources.make (revision 5254) +++ DerivedSources.make (working copy) @@ -32,10 +32,6 @@ $(PORTROOT)/html \ $(PORTROOT)/page \ $(PORTROOT)/page/inspector \ -$(PORTROOT)/svg \ -$(PORTROOT)/xml \ -$(PORTROOT)/ksvg2/svg \ -$(PORTROOT)/ksvg2/events \ $(WebCore) \ $(WebCore)/bindings/js \ $(WebCore)/bindings/v8 \ @@ -1172,5 +1168,5 @@ rm -f $@; \ for i in 1 2 3 4 5 6 7 8 9 10; do \ if test -e $@; then break; fi; \ - perl -w -I $(PORTROOT)/bindings/scripts -I $(WebCore)/ bindings/scripts $(PORTROOT)/bindings/scripts/generate-bindings.pl --defines "$ (FEATURE_DEFINES) LANGUAGE_JAVASCRIPT V8_BINDING" --generator V8 --include ../../../ webkit/pendin g --include ../../../webkit/port/dom --include ../../../webkit/port/ html --inclu de ../../../webkit/port/page --include ../../../webkit/port/xml -- include svg -- include dom --include html --include css --include page --include xml --include plugins --outputdir . $< ; \ + perl -w -I $(PORTROOT)/bindings/scripts -I $(WebCore)/ bindings/scripts $(PORTROOT)/bindings/scripts/generate-bindings.pl --defines "$ (FEATURE_DEFINES) LANGUAGE_JAVASCRIPT V8_BINDING" --generator V8 --include ../../../ webkit/pendin g --include ../../../webkit/port/dom --include ../../../webkit/port/ html --inclu de ../../../webkit/port/page --include svg --include dom --include html --includ e css --include page --include xml --include plugins --outputdir . $< ; \ --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "Chromium-dev" group. To post to this group, send email to chromium-dev@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/chromium-dev?hl=en -~--~~~~--~~--~--~---
[chromium-dev] Re: Mac TestShell weaned from PLATFORM(MAC) and it now renders pages!
Wow good job! Keep up the good work. "Sure, clicking crashes, ..." Ahah! You make me lol. --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "Chromium-dev" group. To post to this group, send email to chromium-dev@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/chromium-dev?hl=en -~--~~~~--~~--~--~---
[chromium-dev] Re: Confirmation dialog (when you close [Alt + F4] ) when multiple tabs are open
A better idea will be to display a countdown 4-3-2-1- in the cancel button: - | Closing... | - | Cancel (3) | <-- button - this way when you click the 'x' button, you can do something else without having to care about it. On Oct 3, 6:33 am, doth <[EMAIL PROTECTED]> wrote: > All, > > Feature request: > - Add a confirmation dialog ( Ok, Cancel ) when the user clicks on > "Close" icon or Alt + F4. > > Benefit: > - This would allow unintended close of all the tabs when the user > clicks on the "Close" button in the browser. > > Do let me know your thoughts. --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "Chromium-dev" group. To post to this group, send email to chromium-dev@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/chromium-dev?hl=en -~--~~~~--~~--~--~---
[chromium-dev] Re: TestShell Mac update
And Good job! Keep up the good work! On Sep 23, 2:59 pm, "Mike Pinkerton" <[EMAIL PROTECTED]> wrote: > Just wanted to give folks a quick update on the Mac status of > TestShell. This morning we got it fully linking and bringing up a > window. Note that to do this, we had to stub out a big chunk of the > net library until we do some better slicing/if-defing around the SSL > code (pulling in the basic http_transaction pulls in a lot). > > It launches, and we were able to work through several asserts and > crashers in the actual TestShell code and posix shared-mem > implementation. We also discovered some misalignment in glue where we > assume skia drawing and the underlying implementation assumes CG. > Fixing those up led to a huge stack smashing crash, but we have a > window that displays a green background, which means that we were able > to get the bulk of infrastructure in place and rendering on-screen. > > Next steps: > - finish networking layer for file and http > - resolve drawing layer incompatibilities through the glue layer > - render a webpage! > > So close! > > -- > Mike Pinkerton > Mac Weenie > [EMAIL PROTECTED] --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "Chromium-dev" group. To post to this group, send email to chromium-dev@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/chromium-dev?hl=en -~--~~~~--~~--~--~---
[chromium-dev] Re: TestShell Mac update
Just got the same error on windows. Try cleaning-up your building folder and try to build again. On Sep 23, 5:03 pm, Hiro <[EMAIL PROTECTED]> wrote: > For me, TestShell doesn't works > > I have a compilation error : > > chromium/src/webkit/../xcodebuild/webkit.build/Debug/generated/ > DerivedSources/v8/bindings/V8Attr.cpp:45: error: 'FastToNativeObject' > is not a member of 'WebCore::V8Proxy' > chromium/src/webkit/../xcodebuild/webkit.build/Debug/generated/ > DerivedSources/v8/bindings/V8Attr.cpp:45: error: expected primary- > expression before '>' token > > And this for a lot of files of V8/bindings > > On 23 sep, 20:59, "Mike Pinkerton" <[EMAIL PROTECTED]> wrote: > > > Just wanted to give folks a quick update on the Mac status of > > TestShell. This morning we got it fully linking and bringing up a > > window. Note that to do this, we had to stub out a big chunk of the > > net library until we do some better slicing/if-defing around the SSL > > code (pulling in the basic http_transaction pulls in a lot). > > > It launches, and we were able to work through several asserts and > > crashers in the actual TestShell code and posix shared-mem > > implementation. We also discovered some misalignment in glue where we > > assume skia drawing and the underlying implementation assumes CG. > > Fixing those up led to a huge stack smashing crash, but we have a > > window that displays a green background, which means that we were able > > to get the bulk of infrastructure in place and rendering on-screen. > > > Next steps: > > - finish networking layer for file and http > > - resolve drawing layer incompatibilities through the glue layer > > - render a webpage! > > > So close! > > > -- > > Mike Pinkerton > > Mac Weenie > > [EMAIL PROTECTED] --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "Chromium-dev" group. To post to this group, send email to chromium-dev@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/chromium-dev?hl=en -~--~~~~--~~--~--~---
[chromium-dev] Custom theme problem: Bookmark bar (Feature)
I just posted my first custom theme for chrome on chromium- discussion: http://groups.google.com/group/chromium-discuss/browse_thread/thread/2f504ad184fa12b9 Forever, there is a little problem with it and the problem is that I can't change the color used to generate the gradient of the bookmark bar. They are actually hard coded in the chrome.dll file. What I will like for the moment is that you move constants kBackgroundColor, kTopBorderColor, kBottomBorderColor, kNewtabBackgroundColor and kNewtabBorderColor that are currently in bookmark_bar_view.cc in a new theme_config.cc and theme_config.h file. Those two new files will then be placed in the theme project. Also, I suggest you to not bother on exporting all the SkColorSetRGB, just write down the color using the old good fashion hexadecimal method. --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "Chromium-dev" group. To post to this group, send email to chromium-dev@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/chromium-dev?hl=en -~--~~~~--~~--~--~---
