Return-Path: X-Original-To: apmail-incubator-bloodhound-dev-archive@minotaur.apache.org Delivered-To: apmail-incubator-bloodhound-dev-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 98B81D86A for ; Sat, 1 Dec 2012 06:42:07 +0000 (UTC) Received: (qmail 3551 invoked by uid 500); 1 Dec 2012 06:42:07 -0000 Delivered-To: apmail-incubator-bloodhound-dev-archive@incubator.apache.org Received: (qmail 3446 invoked by uid 500); 1 Dec 2012 06:42:05 -0000 Mailing-List: contact bloodhound-dev-help@incubator.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: bloodhound-dev@incubator.apache.org Delivered-To: mailing list bloodhound-dev@incubator.apache.org Received: (qmail 3387 invoked by uid 99); 1 Dec 2012 06:42:02 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 01 Dec 2012 06:42:02 +0000 X-ASF-Spam-Status: No, hits=-0.7 required=5.0 tests=RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of olemis@gmail.com designates 209.85.220.175 as permitted sender) Received: from [209.85.220.175] (HELO mail-vc0-f175.google.com) (209.85.220.175) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 01 Dec 2012 06:41:57 +0000 Received: by mail-vc0-f175.google.com with SMTP id fy7so394139vcb.6 for ; Fri, 30 Nov 2012 22:41:36 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type:content-transfer-encoding; bh=PGWGuSu2z6ZYYZikWcK70zlXnOraAmUW8cWNrN61xeE=; b=r1hnyAU5KxWUIcR7hqhu27D1WNT5r2WM2dk8c/+k4Shs3lGu3ZqUkr1Ae9tvjtT7zk Ej2rfn/1yHl6eaG5nyPckfMNnWux747qqbViTeFv+AC2FsGduBLgVPZIcPkh+0B4Zwdb 6u9fnogylQibuX0oZLhRSWpUHwZfoWOXKxwvtl1/vNpgkYCyM+1njyem/sPOVne3nsE3 bcxVHdYj8FhpBPBzOJCAJben8Nv0wJ4FoLPFbPMpruHVUtVpK3bUEOOqmdi1ud80Pawi iNL2m4w6o9rG4hX+dJ4jTd+Si70mnlat6JV/Rnvl0pRmVJdUBvARqvfjh9lM+wQhP2oL 7GRg== MIME-Version: 1.0 Received: by 10.58.12.231 with SMTP id b7mr3234003vec.31.1354344096613; Fri, 30 Nov 2012 22:41:36 -0800 (PST) Received: by 10.58.156.71 with HTTP; Fri, 30 Nov 2012 22:41:36 -0800 (PST) In-Reply-To: References: Date: Sat, 1 Dec 2012 01:41:36 -0500 Message-ID: Subject: Re: Browser, HTML and JS support From: Olemis Lang To: bloodhound-dev@incubator.apache.org Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-Virus-Checked: Checked by ClamAV on apache.org On 11/29/12, Peter Ko=C5=BEelj wrote: > The question of browser, html versions and no-JS support came up recently > in a couple of threads. > This deserves a thread on it own. Here is my proposal: > > HTML VERSION > We should migrate to HTML5. We are already using some of it and should ma= ke > it official (HTML header) > suggestions to get this done in a separate thread . ;) besides I mentioned ... somewhere ... that we might want to include in our pages Google's html5 patch for MSIE plus bootstrap MSIE compatibility hacks . I noticed this while working on #195 , don't remember any previous reply . > DESKTOP BROWSER ("official" support) > - Google Chrome on Windows and OSX > - Mozilla Firefox on Windows and OSX + Opera ;) ... and add GNU/Linux to OS list ... preferably Ubuntu . > - IE on Windows ... with all the associated challenges . btw , is anybody testing BH on Windows + MSIE ? > - Safari on OSX > > For all browser only major versions released in last 18months > are officially supported. > Compatibility with other or older browser is welcomed but we should not > spend extra energy on it or even worse, design UI for it. > ... afaicr that's what we've been doing so far , at least most of the time = . > TABLETS and SMART PHONES > Responsive layout is nice but to actually support specific devices/browse= r > would require that we actually posses those devices for development and > testing. > For now I would not support specific devices or platforms. All we can say > "screen size adaptable" or something. > fwiw +1 > JAVASCRIPT > Is required! We should not spend time and energy on this right now. We ha= ve > much bigger things to worry about. > No javascript fallbacks can always be added later, and it also decreases > the risk for designing to the minimal common denominator which is extreme= ly > low for non-javascript variant. > -1 Reasons mentioned in previous messages. BH has to work even if JS is not available , not 100% of the functionalities will be available though . --=20 Regards, Olemis. Blog ES: http://simelo-es.blogspot.com/ Blog EN: http://simelo-en.blogspot.com/ Featured article: