From owner-freebsd-chromium@FreeBSD.ORG Mon Apr 30 11:06:44 2012 Return-Path: Delivered-To: chromium@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 42F4D1065674 for ; Mon, 30 Apr 2012 11:06:44 +0000 (UTC) (envelope-from owner-bugmaster@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 2D2348FC08 for ; Mon, 30 Apr 2012 11:06:44 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.5/8.14.5) with ESMTP id q3UB6ic4053432 for ; Mon, 30 Apr 2012 11:06:44 GMT (envelope-from owner-bugmaster@FreeBSD.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.5/8.14.5/Submit) id q3UB6hpV053430 for chromium@FreeBSD.org; Mon, 30 Apr 2012 11:06:43 GMT (envelope-from owner-bugmaster@FreeBSD.org) Date: Mon, 30 Apr 2012 11:06:43 GMT Message-Id: <201204301106.q3UB6hpV053430@freefall.freebsd.org> X-Authentication-Warning: freefall.freebsd.org: gnats set sender to owner-bugmaster@FreeBSD.org using -f From: FreeBSD bugmaster To: chromium@FreeBSD.org Cc: Subject: Current problem reports assigned to chromium@FreeBSD.org X-BeenThere: freebsd-chromium@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: FreeBSD-specific Chromium issues List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 30 Apr 2012 11:06:44 -0000 Note: to view an individual PR, use: http://www.freebsd.org/cgi/query-pr.cgi?pr=(number). The following is a listing of current problems submitted by FreeBSD users. These represent problem reports covering all versions including experimental development code and obsolete releases. S Tracker Resp. Description -------------------------------------------------------------------------------- o ports/165637 chromium www/chromium: 17.0.963.56 fails to find some ns plugin o ports/165636 chromium www/chromium: 17.0.963.56: unable to import data from o ports/165635 chromium www/chromium: 17.0.963.56: proxy isn't read by chrome o ports/165634 chromium www/chromium : 17.0.963.56 doesn't show physical print 4 problems total. From owner-freebsd-chromium@FreeBSD.ORG Mon Apr 30 11:07:24 2012 Return-Path: Delivered-To: freebsd-chromium@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id A97B31065670 for ; Mon, 30 Apr 2012 11:07:24 +0000 (UTC) (envelope-from owner-bugmaster@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 7A36B8FC1A for ; Mon, 30 Apr 2012 11:07:24 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.5/8.14.5) with ESMTP id q3UB7OKS053824 for ; Mon, 30 Apr 2012 11:07:24 GMT (envelope-from owner-bugmaster@FreeBSD.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.5/8.14.5/Submit) id q3UB7NMA053822 for freebsd-chromium@FreeBSD.org; Mon, 30 Apr 2012 11:07:23 GMT (envelope-from owner-bugmaster@FreeBSD.org) Date: Mon, 30 Apr 2012 11:07:23 GMT Message-Id: <201204301107.q3UB7NMA053822@freefall.freebsd.org> X-Authentication-Warning: freefall.freebsd.org: gnats set sender to owner-bugmaster@FreeBSD.org using -f From: FreeBSD bugmaster To: freebsd-chromium@FreeBSD.org Cc: Subject: Current problem reports assigned to freebsd-chromium@FreeBSD.org X-BeenThere: freebsd-chromium@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: FreeBSD-specific Chromium issues List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 30 Apr 2012 11:07:24 -0000 Note: to view an individual PR, use: http://www.freebsd.org/cgi/query-pr.cgi?pr=(number). The following is a listing of current problems submitted by FreeBSD users. These represent problem reports covering all versions including experimental development code and obsolete releases. S Tracker Resp. Description -------------------------------------------------------------------------------- o ports/167402 chromium www/chromium doesn't build WITH_PULSEAUDIO, looks like 1 problem total. From owner-freebsd-chromium@FreeBSD.ORG Mon Apr 30 11:20:54 2012 Return-Path: Delivered-To: freebsd-chromium@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 4CC1D1065670; Mon, 30 Apr 2012 11:20:54 +0000 (UTC) (envelope-from rene@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 1E7688FC12; Mon, 30 Apr 2012 11:20:54 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.5/8.14.5) with ESMTP id q3UBKrXx070220; Mon, 30 Apr 2012 11:20:54 GMT (envelope-from rene@freefall.freebsd.org) Received: (from rene@localhost) by freefall.freebsd.org (8.14.5/8.14.5/Submit) id q3UBKrsZ070211; Mon, 30 Apr 2012 11:20:53 GMT (envelope-from rene) Date: Mon, 30 Apr 2012 11:20:53 GMT Message-Id: <201204301120.q3UBKrsZ070211@freefall.freebsd.org> To: bowlapplefork@yahoo.com, rene@FreeBSD.org, freebsd-chromium@FreeBSD.org From: rene@FreeBSD.org Cc: Subject: Re: ports/167402: www/chromium doesn't build WITH_PULSEAUDIO, looks like X-BeenThere: freebsd-chromium@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: FreeBSD-specific Chromium issues List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 30 Apr 2012 11:20:54 -0000 Synopsis: www/chromium doesn't build WITH_PULSEAUDIO, looks like State-Changed-From-To: open->closed State-Changed-By: rene State-Changed-When: Mon Apr 30 11:16:41 UTC 2012 State-Changed-Why: Closed, the provided suggestion is both ambigious (how many revisions) and bogus because any earlier version of chromium has security problems. The patch at http://code.google.com/p/chromium/issues/detail?id=111392 which was mentioned in the freebsd-chromium@ mailing list at http://lists.freebsd.org/pipermail/freebsd-chromium/2012-April/000396.html is under test. http://www.freebsd.org/cgi/query-pr.cgi?pr=167402 From owner-freebsd-chromium@FreeBSD.ORG Mon Apr 30 11:26:42 2012 Return-Path: Delivered-To: chromium@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 7AAF5106564A; Mon, 30 Apr 2012 11:26:42 +0000 (UTC) (envelope-from rene@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 4FA328FC16; Mon, 30 Apr 2012 11:26:42 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.5/8.14.5) with ESMTP id q3UBQgrY075563; Mon, 30 Apr 2012 11:26:42 GMT (envelope-from rene@freefall.freebsd.org) Received: (from rene@localhost) by freefall.freebsd.org (8.14.5/8.14.5/Submit) id q3UBQgCL075559; Mon, 30 Apr 2012 11:26:42 GMT (envelope-from rene) Date: Mon, 30 Apr 2012 11:26:42 GMT Message-Id: <201204301126.q3UBQgCL075559@freefall.freebsd.org> To: yuri@tsoft.com, rene@FreeBSD.org, chromium@FreeBSD.org From: rene@FreeBSD.org Cc: Subject: Re: ports/165634: www/chromium : 17.0.963.56 doesn't show physical printer X-BeenThere: freebsd-chromium@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: FreeBSD-specific Chromium issues List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 30 Apr 2012 11:26:42 -0000 Synopsis: www/chromium : 17.0.963.56 doesn't show physical printer State-Changed-From-To: open->feedback State-Changed-By: rene State-Changed-When: Mon Apr 30 11:25:55 UTC 2012 State-Changed-Why: Is this still a problem with 18.0.1025.162 ? http://www.freebsd.org/cgi/query-pr.cgi?pr=165634 From owner-freebsd-chromium@FreeBSD.ORG Mon Apr 30 15:47:22 2012 Return-Path: Delivered-To: chromium@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 9600C1065672 for ; Mon, 30 Apr 2012 15:47:22 +0000 (UTC) (envelope-from evanm@google.com) Received: from mail-yx0-f182.google.com (mail-yx0-f182.google.com [209.85.213.182]) by mx1.freebsd.org (Postfix) with ESMTP id 2EDD98FC0C for ; Mon, 30 Apr 2012 15:47:22 +0000 (UTC) Received: by yenl9 with SMTP id l9so1657887yen.13 for ; Mon, 30 Apr 2012 08:47:21 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type :content-transfer-encoding:x-system-of-record; bh=Uf0zfmiul03oHBR0eAoUEyljZWQWku9UsWf1hQrR4bo=; b=h5KdAFY5IPtJEulAe5jgxrhLXv4mdjemxKBRvsa6H6QS3BQiJcaiXYx2hhum3yyeS5 jOOCplq8XfFlMs9vGAu3DyK2AftPqoIidQXrU3jR6T5zX+cROANf7YL6ZJnGCcOZ/2EA FCzXggYReFjdMLWMLr9p+o1kiTXTIXbSbQpLbcKpY4esQlUwn1J8C8DpDPytaL4PTK7N BaiMjJmIOF/3vdSnz/bWF2Ppz5xdpOA0j5XcOfM7Q8fJNFTexe9PkinENbmnqWVC+eYj 3ruz4rYcSkusIe/ZH9S0kW4IpcRWQyOMMvMDJxfLAzhrJQAVg8rPj6uss/zfSjVYqOB0 s9mw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type :content-transfer-encoding:x-system-of-record:x-gm-message-state; bh=Uf0zfmiul03oHBR0eAoUEyljZWQWku9UsWf1hQrR4bo=; b=lxpsyB0trW01bbmnGiaoEP4O7GlUcHbZLB6WrMakmxWfMayGgsZ4aWq7YkUfIhOxuy CYSICEkWGN+a93QeP6L3SNNXcNuEAydXq/3j3wQ+8qcscMINAKmhkHCXT67bR4jMgbXK bSB+Dip5yf2SW0FpFjy4uQ4GsvRi9YpzWbyb9BlWN4OAvNWS6Tge5IDgIeDN8a97qT6W 0MVB+6UJiEkEyAWZ2WKXBn7+d48ixMsfUNAQpJuteVy34PuJyROf9qnN7Sk0/s0MVT/a HNYe/eICSxjBczxhjaocr7YfAYWzsHNBfjM2lPAHaPlojHiI2qD4iAplXOZU4vxRxzPC EjcQ== Received: by 10.236.78.70 with SMTP id f46mr22309143yhe.99.1335800841394; Mon, 30 Apr 2012 08:47:21 -0700 (PDT) MIME-Version: 1.0 Received: by 10.236.78.70 with SMTP id f46mr22309126yhe.99.1335800841276; Mon, 30 Apr 2012 08:47:21 -0700 (PDT) Sender: evanm@google.com Received: by 10.101.156.21 with HTTP; Mon, 30 Apr 2012 08:47:21 -0700 (PDT) In-Reply-To: <20120428144745.GA40844@onelab2.iet.unipi.it> References: <20120428144745.GA40844@onelab2.iet.unipi.it> Date: Mon, 30 Apr 2012 08:47:21 -0700 X-Google-Sender-Auth: vRdajpDd6hFBFODYfDitrja6oWM Message-ID: From: Evan Martin To: Luigi Rizzo Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable X-System-Of-Record: true X-Gm-Message-State: ALoCoQl0bGTD3LM3FTHXZuU2Jt7l6KKEXF5l+ETmr/VIg4grRtslVNCOIsWhu5vmv5NmDrDi8+C5XYhZXDnLjjdbI1qfs4i+wuxJ5NKgj9hgi4me2gbA47cDEp1O7JaNxB3LXjNsyMZHyRux/BErtDBU5Isg7oBS1A== Cc: chromium@freebsd.org, hackers@freebsd.org Subject: Re: how to display C sources in Chromium (file:/// only) X-BeenThere: freebsd-chromium@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: FreeBSD-specific Chromium issues List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 30 Apr 2012 15:47:22 -0000 On Sat, Apr 28, 2012 at 7:47 AM, Luigi Rizzo wrote: > (hoping this is of interest for hackers- too) > > One of the most annoying features of chromium is that it downloads > instead of displaying various types of files (.c, .h and so on). This has long annoyed me too! > it seems that a partial fix can be achieved by arring the list of > types we want to display to the array > > =A0 =A0static const char* const supported_non_image_types[] =3D { > =A0 =A0 =A0 =A0... > + =A0 =A0 =A0 "text/x-csrc", > + =A0 =A0 =A0 "text/x-chdr", > =A0 =A0 =A0 =A0... > =A0 =A0} There's a comment at the end of the block: // Note: ADDING a new type here will probably render it AS HTML. This can // result in cross site scripting. I wonder how to tell? If you follow the references back from the definition of this variable it appears to end up used here: http://code.google.com/searchframe#OAMlx_jo-ck/src/third_party/WebKit/Sourc= e/WebCore/loader/FrameLoader.cpp&exact_package=3Dchromium&ct=3Drc&cd=3D10&q= =3DIsSupportedNonImageMimeType&l=3D859 which just indicates it's used when WebKit is deciding whether to inline the content or not. It seems to me like you could adjust the code in MimeUtil::IsSupportedNonImageMimeType to always return true for any text/* mime type. From owner-freebsd-chromium@FreeBSD.ORG Mon Apr 30 16:24:32 2012 Return-Path: Delivered-To: freebsd-chromium@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 8BF42106566C for ; Mon, 30 Apr 2012 16:24:32 +0000 (UTC) (envelope-from r.c.ladan@gmail.com) Received: from mail-we0-f182.google.com (mail-we0-f182.google.com [74.125.82.182]) by mx1.freebsd.org (Postfix) with ESMTP id 115378FC12 for ; Mon, 30 Apr 2012 16:24:31 +0000 (UTC) Received: by weyt57 with SMTP id t57so2436230wey.13 for ; Mon, 30 Apr 2012 09:24:31 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=sender:message-id:date:from:organization:user-agent:mime-version:to :cc:subject:references:in-reply-to:content-type :content-transfer-encoding; bh=rnMVJmoIQYuZVL0nlggFLQmUKQBnCiH9DTrVmO27VS8=; b=jfv2QS8DK3Y4jpmY3uAAw/oICsbUEFIosIiHMguZdUNb+WHU7keNhcn6W0zsnFTmrX Qht8dHnVTNT+6LOdn6tKMiZ7FhNCWJl2ObKfMzpKzj7l8fpG9LuXMtjVKmUzH3p4stif V1A0ub3iEZ/ksz/BcJUPLQxW5103yekBNKUI28tQvQaeYGYFhMzfpuKhX3HGRV8387uI Z5O26Qlah1+T2sPy4MKP44ICW1ew52BDBAwSZemrxBCDgOEIaw3TxlY4GXU34/UK/7Uq Hz48qV+hGSCTgUXwPIl1rfqGUCqYjyzcMCw6pUJgQb+alNaQ3Y3fkx/tCy7A+2l7OglC IDbg== Received: by 10.180.104.137 with SMTP id ge9mr19064723wib.20.1335803070898; Mon, 30 Apr 2012 09:24:30 -0700 (PDT) Received: from [192.168.1.15] (ip18-43-209-87.adsl2.static.versatel.nl. [87.209.43.18]) by mx.google.com with ESMTPS id l5sm29354543wia.11.2012.04.30.09.24.29 (version=TLSv1/SSLv3 cipher=OTHER); Mon, 30 Apr 2012 09:24:29 -0700 (PDT) Sender: =?UTF-8?Q?Ren=C3=A9_Ladan?= Message-ID: <4F9EBCBC.8030207@freebsd.org> Date: Mon, 30 Apr 2012 18:24:28 +0200 From: Rene Ladan Organization: The FreeBSD Project User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:12.0) Gecko/20120426 Thunderbird/12.0 MIME-Version: 1.0 To: meowthink@gmail.com References: In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-chromium@freebsd.org Subject: Re: Chromium 18 w/PulseAudio X-BeenThere: freebsd-chromium@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: FreeBSD-specific Chromium issues List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 30 Apr 2012 16:24:32 -0000 On 07-04-2012 11:39, Meowthink wrote: > Hello all, > > There's a bug in current chromium's codebase, preventing compiling > with pulseaudio. > > nullnix.backup posted a patch here: > http://code.google.com/p/chromium/issues/detail?id=111392 > I just committed this patch to the Chromium port. Rene -- http://www.rene-ladan.nl:8080/ GPG fingerprint = ADBC ECCD EB5F A6B4 549F 600D 8C9E 647A E564 2BFC (subkeys.pgp.net) From owner-freebsd-chromium@FreeBSD.ORG Mon Apr 30 19:03:23 2012 Return-Path: Delivered-To: chromium@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id DF340106566C; Mon, 30 Apr 2012 19:03:23 +0000 (UTC) (envelope-from luigi@onelab2.iet.unipi.it) Received: from onelab2.iet.unipi.it (onelab2.iet.unipi.it [131.114.59.238]) by mx1.freebsd.org (Postfix) with ESMTP id 9EA468FC0C; Mon, 30 Apr 2012 19:03:23 +0000 (UTC) Received: by onelab2.iet.unipi.it (Postfix, from userid 275) id 9B2D97300A; Mon, 30 Apr 2012 21:23:05 +0200 (CEST) Date: Mon, 30 Apr 2012 21:23:05 +0200 From: Luigi Rizzo To: Evan Martin Message-ID: <20120430192305.GA72227@onelab2.iet.unipi.it> References: <20120428144745.GA40844@onelab2.iet.unipi.it> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4.2.3i Cc: chromium@freebsd.org, hackers@freebsd.org Subject: Re: how to display C sources in Chromium (file:/// only) X-BeenThere: freebsd-chromium@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: FreeBSD-specific Chromium issues List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 30 Apr 2012 19:03:24 -0000 On Mon, Apr 30, 2012 at 08:47:21AM -0700, Evan Martin wrote: > On Sat, Apr 28, 2012 at 7:47 AM, Luigi Rizzo wrote: > > (hoping this is of interest for hackers- too) > > > > One of the most annoying features of chromium is that it downloads > > instead of displaying various types of files (.c, .h and so on). > > This has long annoyed me too! > > > it seems that a partial fix can be achieved by arring the list of > > types we want to display to the array > > > > ? ?static const char* const supported_non_image_types[] = { > > ? ? ? ?... > > + ? ? ? "text/x-csrc", > > + ? ? ? "text/x-chdr", > > ? ? ? ?... > > ? ?} > > There's a comment at the end of the block: > // Note: ADDING a new type here will probably render it AS HTML. This can > // result in cross site scripting. > I wonder how to tell? I think that the comment is partially or completely wrong. As one can easily verify, if the server reports "Content-Type: text/plain" the data is displayed as plain text even if it contains some html. There must be another layer which decides how to render the content but this list is only a YES/NO indication. > If you follow the references back from the definition of this variable > it appears to end up used here: > http://code.google.com/searchframe#OAMlx_jo-ck/src/third_party/WebKit/Source/WebCore/loader/FrameLoader.cpp&exact_package=chromium&ct=rc&cd=10&q=IsSupportedNonImageMimeType&l=859 > which just indicates it's used when WebKit is deciding whether to > inline the content or not. > > It seems to me like you could adjust the code in > MimeUtil::IsSupportedNonImageMimeType to always return true for any > text/* mime type. I wouldn't be surprised if there were an easy override in some config file. This issue has been mentioned for ages on the chrome issue database, often referring at the correct behaviour of other browser e.g. Firefox. Some relevant entries: http://code.google.com/p/chromium/issues/detail?id=24675 http://code.google.com/p/chromium/issues/detail?id=118204 http://code.google.com/p/chromium/issues/detail?id=106150 But i remember seeing many others, some closed, some with a long trail eventually mentioning deep security or architectural issues as a motivation not to implement the feature. After finding out the .local/share/mime/globs2 trick, i really believe that those answers really meant "I have no idea why it is so, and i am too afraid of breaking something to even consider changing things" Annoying but understandable given the size of the code cheers luigi