IETF Logo Mail Archive

Re: [TOOLS-DEVELOPMENT] CSS for RFCs SOW

"Joe Hildebrand (jhildebr)" <jhildebr@cisco.com> Mon, 18 July 2016 06:57 UTC

Return-Path: <jhildebr@cisco.com>
X-Original-To: tools-development@ietfa.amsl.com
Delivered-To: tools-development@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3F25512D0B3 for <tools-development@ietfa.amsl.com>; Sun, 17 Jul 2016 23:57:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -15.808
X-Spam-Level:
X-Spam-Status: No, score=-15.808 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-1.287, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cisco.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id FnsLvvepycdO for <tools-development@ietfa.amsl.com>; Sun, 17 Jul 2016 23:57:11 -0700 (PDT)
Received: from rcdn-iport-3.cisco.com (rcdn-iport-3.cisco.com [173.37.86.74]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 8E89112B02D for <tools-development@ietf.org>; Sun, 17 Jul 2016 23:57:11 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=1562; q=dns/txt; s=iport; t=1468825031; x=1470034631; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-id:content-transfer-encoding: mime-version; bh=Vpv9XaxTNdpNrjpbk7KR/L9qXekR9JupHIMUv2EOyHE=; b=dKU3eblKWC8/qoc59NA8oTqtNE4b0hL2Jo9m5MV5xj9sKbtuOyZz9eZx Yj18kLTJHtjwti3eexvomsN0lv0H0lwEsxLnYUvvUuEWRaWrISd7JlsKJ 65oDkJZUmPUPUwtesl27FYZc1Xp9w21CvC5nLDXt9fcAF1+/HfEYTefpM U=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0B1BQBcfYxX/5FdJa1cgz9WfAa4dIF5IoV4AoEuORMBAQEBAQEBZSeEXAEBBAEBASUTNAsFCwIBCBgeECcLJQIEDgWIFgMPCA6/DQEBAQEBAQEBAQEBAQEBAQEBAQEBARcFhiqBeIJVgkOBfYMsgi8FmSQBhhKITI83kB0BIAEzg3NuAYY6fwEBAQ
X-IronPort-AV: E=Sophos;i="5.28,382,1464652800"; d="scan'208";a="130562727"
Received: from rcdn-core-9.cisco.com ([173.37.93.145]) by rcdn-iport-3.cisco.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 18 Jul 2016 06:56:59 +0000
Received: from XCH-RTP-005.cisco.com (xch-rtp-005.cisco.com [64.101.220.145]) by rcdn-core-9.cisco.com (8.14.5/8.14.5) with ESMTP id u6I6uxxD009384 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=FAIL); Mon, 18 Jul 2016 06:56:59 GMT
Received: from xch-rtp-001.cisco.com (64.101.220.141) by XCH-RTP-005.cisco.com (64.101.220.145) with Microsoft SMTP Server (TLS) id 15.0.1210.3; Mon, 18 Jul 2016 02:56:58 -0400
Received: from xch-rtp-001.cisco.com ([64.101.220.141]) by XCH-RTP-001.cisco.com ([64.101.220.141]) with mapi id 15.00.1210.000; Mon, 18 Jul 2016 02:56:58 -0400
From: "Joe Hildebrand (jhildebr)" <jhildebr@cisco.com>
To: Julian Reschke <julian.reschke@gmx.de>
Thread-Topic: [TOOLS-DEVELOPMENT] CSS for RFCs SOW
Thread-Index: AQHR4LrKT3gk7EFPVECqP/9NPfsJTaAeBL6A
Date: Mon, 18 Jul 2016 06:56:58 +0000
Message-ID: <1176B858-CD4F-4A81-BA59-B639BCDD2046@cisco.com>
References: <C67A7147-8A55-4E68-8B81-2CC2586D85A1@vigilsec.com> <424bc5bb-d32a-d823-54aa-df1f69a3e238@rfc-editor.org> <54BC881A-0B9C-4553-8433-1FB1DADA4E9F@vigilsec.com> <AFE01F67-9610-471E-8458-83B67A212B5E@vigilsec.com> <f8afa332-1f24-40e9-9ee3-886a67d3ce0e@gmx.de>
In-Reply-To: <f8afa332-1f24-40e9-9ee3-886a67d3ce0e@gmx.de>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-mailer: Apple Mail (2.3124)
x-ms-exchange-messagesentrepresentingtype: 1
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [10.61.98.15]
Content-Type: text/plain; charset="us-ascii"
Content-ID: <7CCD6065317BFA4E84917B97EAB7E220@emea.cisco.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/tools-development/QShNmGMtxBp0Acg6t3Em0t9DemU>
Cc: IETF Tools Development <tools-development@ietf.org>
Subject: Re: [TOOLS-DEVELOPMENT] CSS for RFCs SOW
X-BeenThere: tools-development@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Tools Development list server <tools-development.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tools-development>, <mailto:tools-development-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/tools-development/>
List-Post: <mailto:tools-development@ietf.org>
List-Help: <mailto:tools-development-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tools-development>, <mailto:tools-development-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 18 Jul 2016 06:57:13 -0000

I'd suggest not over-specifying here.  Having CSS that's not understood (within reasonable size limits) doesn't hurt anything.  Having standardized CSS that isn't widely-implemeneted yet (such as the printing bits) may help a potential HTML->PDF conversion, and may push more browsers to implement those bits one day.  Finally, there are some places where using browser-specific CSS (like -moz-user-select) can increase the number of older browsers that are supported.


> On Jul 18, 2016, at 8:08 AM, Julian Reschke <julian.reschke@gmx.de> wrote:
> 
> On 2016-07-05 20:20, Russ Housley wrote:
>> With the recent change to the CSS for RFCs SOW, I think this is ready to go out as an RFP.  Does anyone concerns?
>> 
>> Russ
> 
> Another thing that just occurred to me is that the text doesn't say anything specific about compliance to CSS specifications (and which), use of browser-specific extensions, and browser support in general.
> 
> This can be relevant as CSS comes in modules, and not all of them are at the state of standardization.
> 
> (In particular, <https://tools.ietf.org/html/draft-iab-rfc-css-01#section-7.16> asks for functionality not available in standard CSS today).
> 
> Best regards, Julian
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> _______________________________________________
> TOOLS-DEVELOPMENT mailing list
> TOOLS-DEVELOPMENT@ietf.org
> https://www.ietf.org/mailman/listinfo/tools-development

-- 
Joe Hildebrand

v2.23.0 | Report a Bug | By Email