[chromium-dev] Re: Autofill design document
As I read this it will only autofill one field? What we need is a bookmark for the web form, stored with which should be all the field names and the values that were saved by the user when the bookmark was created. When one is on the page, an icon should change to show there are one or more possible sets of data to fill this form with. If the user clicks the button, all fields are filled and the form is submitted (optional). This would also replace the current password manager. (See Roboform for a working example of how to do it!) Chris On Oct 14, 11:04 pm, Adam Barth [EMAIL PROTECTED] wrote: What about forms created after WebFrameLoaderClient::dispatchDidFinishDocumentLoad? For example, if you click the reply button on Gmail? Seems like you're better off hooking the focusing of input elements... Adam On Tue, Oct 14, 2008 at 2:58 PM, Peterson Trethewey [EMAIL PROTECTED] wrote: http://dev.chromium.org/developers/design-documents/form-autofill --pt --~--~-~--~~~---~--~~ 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] How to add new Hunspell dictionaries
Hi, We have an experimental Hunspell dictionary and affix file for Turkish, What is the procedure to add it to Chromium? Currently we have a working Firefox extension in: http://code.google.com/p/tr-spell/ Mehmet. --~--~-~--~~~---~--~~ 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: Autofill design document
Tying this in with bookmarks seems strange to me. form entries organized by the name of the field specified in html get stored in the web database. - this sounds scary. What is the web database? Do you mean the Web Data SQLite database under the profile? Saying the web database makes it sound like we're sending all your data to Google Also, under the security/privacy considerations section: It sounds like you want to have form autofill, but not actually fill stuff in until the user hits submit. While nice in theory, I'm not sure how you exactly get this to work without causing unintended consequences. E.g. there may well be some forms that try to do validation before you hit submit, e.g. submit button is disabled until some javascript runs to make sure that some field is of a proper form - the user will be entirely confused because it will appear to them that the field is properly filled out. I don't think any of this really applies until you start filling out the entire form, rather than just completing the field the user is typing... in that scenario though, I think it would be better to ask the user if they want the form filled in, and then just fill it in. -Ian On Wed, Oct 15, 2008 at 5:43 AM, Chris G [EMAIL PROTECTED] wrote: As I read this it will only autofill one field? What we need is a bookmark for the web form, stored with which should be all the field names and the values that were saved by the user when the bookmark was created. When one is on the page, an icon should change to show there are one or more possible sets of data to fill this form with. If the user clicks the button, all fields are filled and the form is submitted (optional). This would also replace the current password manager. (See Roboform for a working example of how to do it!) Chris On Oct 14, 11:04 pm, Adam Barth [EMAIL PROTECTED] wrote: What about forms created after WebFrameLoaderClient::dispatchDidFinishDocumentLoad? For example, if you click the reply button on Gmail? Seems like you're better off hooking the focusing of input elements... Adam On Tue, Oct 14, 2008 at 2:58 PM, Peterson Trethewey [EMAIL PROTECTED] wrote: http://dev.chromium.org/developers/design-documents/form-autofill --pt --~--~-~--~~~---~--~~ 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: Autofill design document
On Wed, Oct 15, 2008 at 9:09 AM, Ian Fette [EMAIL PROTECTED] wrote: It sounds like you want to have form autofill, but not actually fill stuff in until the user hits submit. While nice in theory, I'm not sure how you exactly get this to work without causing unintended consequences. E.g. there may well be some forms that try to do validation before you hit submit, e.g. submit button is disabled until some javascript runs to make sure that some field is of a proper form - the user will be entirely confused because it will appear to them that the field is properly filled out. I don't think any of this really applies until you start filling out the entire form, rather than just completing the field the user is typing... in that scenario though, I think it would be better to ask the user if they want the form filled in, and then just fill it in. I agree. There are too many gotchas with trying to fake up filling in a form. We should apply the same standards to this as we do to autofilled passwords/usernames w.r.t. when we're willing to autofill information without user action, versus with it. For example, perhaps we will re-fill information on a form you've been to before without any user action, but on a not-visited page, we'll make the user press a button to fill the form. PK --~--~-~--~~~---~--~~ 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: Autofill design document
FYI, our plan here is to start with a simple system similar to that in IE and Firefox - offering autocompletions for values filled into individual fields. We can get more ambitious once we pass this first hurdle. -Ben On Wed, Oct 15, 2008 at 10:18 AM, Peter Kasting [EMAIL PROTECTED] wrote: On Wed, Oct 15, 2008 at 9:09 AM, Ian Fette [EMAIL PROTECTED] wrote: It sounds like you want to have form autofill, but not actually fill stuff in until the user hits submit. While nice in theory, I'm not sure how you exactly get this to work without causing unintended consequences. E.g. there may well be some forms that try to do validation before you hit submit, e.g. submit button is disabled until some javascript runs to make sure that some field is of a proper form - the user will be entirely confused because it will appear to them that the field is properly filled out. I don't think any of this really applies until you start filling out the entire form, rather than just completing the field the user is typing... in that scenario though, I think it would be better to ask the user if they want the form filled in, and then just fill it in. I agree. There are too many gotchas with trying to fake up filling in a form. We should apply the same standards to this as we do to autofilled passwords/usernames w.r.t. when we're willing to autofill information without user action, versus with it. For example, perhaps we will re-fill information on a form you've been to before without any user action, but on a not-visited page, we'll make the user press a button to fill the form. PK --~--~-~--~~~---~--~~ 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] Compilation Errors
Hi,
I am compiling chrome in VC 2005 SP1 (Windows XP). I am getting too much errors.
ERROR SET 1
Cannot open include file: 'config.h': No such file or directory
ERROR SET 2
5c:\google\chromium\src\third_party\WebKit\JavaScriptCore\wtf/MathExtras.h(96)
: error C2143: syntax error : missing ')' before '=='
5c:\google\chromium\src\third_party\WebKit\JavaScriptCore\wtf/MathExtras.h(96)
: error C2143: syntax error : missing ')' before '=='
5c:\google\chromium\src\third_party\WebKit\JavaScriptCore\wtf/MathExtras.h(96)
: error C2059: syntax error : 'constant'
5c:\google\chromium\src\third_party\WebKit\JavaScriptCore\wtf/MathExtras.h(96)
: error C2059: syntax error : ')'
5c:\google\chromium\src\third_party\WebKit\JavaScriptCore\wtf/MathExtras.h(96)
: error C2059: syntax error : ')'
5c:\google\chromium\src\third_party\WebKit\JavaScriptCore\wtf/MathExtras.h(96)
: error C2143: syntax error : missing ';' before '{'
5c:\google\chromium\src\third_party\WebKit\JavaScriptCore\wtf/MathExtras.h(96)
: error C2447: '{' : missing function header (old-style formal list?)
5c:\google\chromium\src\third_party\WebKit\JavaScriptCore\wtf/MathExtras.h(97)
: error C2556: 'bool _isnan(double)'
ERROR 3
fatal error C1189: #error : You must include config.h before TreeShared.h
--ibrar
--~--~-~--~~~---~--~~
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
-~--~~~~--~~--~--~---
