Summary: | WebDocument doesn't export document language to outside users. | ||||||
---|---|---|---|---|---|---|---|
Product: | WebKit | Reporter: | Brian White <bcwhite> | ||||
Component: | WebKit Misc. | Assignee: | Brian White <bcwhite> | ||||
Status: | RESOLVED FIXED | ||||||
Severity: | Normal | CC: | abarth, dglazkov, fishd, jamesr, tkent+wkapi, webkit.review.bot | ||||
Priority: | P2 | ||||||
Version: | 528+ (Nightly build) | ||||||
Hardware: | Unspecified | ||||||
OS: | Unspecified | ||||||
Attachments: |
|
Description
Brian White
2012-10-01 14:02:28 PDT
Created attachment 166709 [details]
Patch
Please wait for approval from abarth@webkit.org, dglazkov@chromium.org, fishd@chromium.org, jamesr@chromium.org or tkent@chromium.org before submitting, as this patch contains changes to the Chromium public API. See also https://trac.webkit.org/wiki/ChromiumWebKitAPI. Comment on attachment 166709 [details] Patch Clearing flags on attachment: 166709 Committed r130191: <http://trac.webkit.org/changeset/130191> All reviewed patches have been landed. Closing bug. Please note that Content-Language is not "document language". It's "intended audience language". This distinction becomes of importance when dealing with a language textbook, for example. Brian, would you be willing to add a comment to that effect to the API header? Interesting! Unexpected, but understandable. The patch has been accepted and "landed" so I assume that means I can't just submit a new patch with the comment. How do I proceed? -- Brian Please create a new bug and attach the patch that adds the comment. You can link from this bug to that bug by including the URL in a comment. |