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 DB24CEAA2 for ; Wed, 28 Nov 2012 05:49:51 +0000 (UTC) Received: (qmail 86115 invoked by uid 500); 28 Nov 2012 05:49:51 -0000 Delivered-To: apmail-incubator-bloodhound-dev-archive@incubator.apache.org Received: (qmail 86038 invoked by uid 500); 28 Nov 2012 05:49:50 -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 86010 invoked by uid 99); 28 Nov 2012 05:49:49 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 28 Nov 2012 05:49:49 +0000 X-ASF-Spam-Status: No, hits=-0.4 required=5.0 tests=PLING_QUERY,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.212.47 as permitted sender) Received: from [209.85.212.47] (HELO mail-vb0-f47.google.com) (209.85.212.47) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 28 Nov 2012 05:49:45 +0000 Received: by mail-vb0-f47.google.com with SMTP id e21so10697202vbm.6 for ; Tue, 27 Nov 2012 21:49:24 -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; bh=Z0ZYHuZd+N1b6QNEaj31kZj9Kj28UAM5Fgscb9fhA3Y=; b=k1hDQsWE6bRO5u9XPnPomPkxyP9KHBt/yH7yt5PrdZIJteD6xoLTUPFtFzCVSJn/hM FuXBK0MkUIXn1eoGcM9IXDO3Nvo2dw8+hw64enTP1N1CqUNYQQjAPhJYc9mi9lRqVgqf SQ6bUfoYrldLWdROsQQY5bk0FR0oUJ8ADdy7kyMnle7u7MLY8Xg5fO+kXD+9Cmy9VB21 2ePcAEo1sk8TgL889kmVchB05cCZjU55MPJK3eaQP6BYgW94PgogEelUzEpFAUBM8ZuO LjbYD9pUdVv4cHq9uQop+6+UOcrljkgHTLqjgE+m/pQo1NFt1kqY0zVaM9nfgzlfL8U0 62gA== MIME-Version: 1.0 Received: by 10.58.12.231 with SMTP id b7mr28545850vec.31.1354081764326; Tue, 27 Nov 2012 21:49:24 -0800 (PST) Received: by 10.58.156.71 with HTTP; Tue, 27 Nov 2012 21:49:24 -0800 (PST) In-Reply-To: <50B4F8F0.7060409@wandisco.com> References: <055.ac285719fa21c61ba176d46695d3a2ec@incubator.apache.org> <070.d2787e2eb8fa2003eb3b3cdd9d4fad9d@incubator.apache.org> <50B4F8F0.7060409@wandisco.com> Date: Wed, 28 Nov 2012 00:49:24 -0500 Message-ID: Subject: Re: [Apache Bloodhound] #279: Images rendered in activity feed ? Oh My ! From: Olemis Lang To: bloodhound-dev@incubator.apache.org Content-Type: text/plain; charset=ISO-8859-1 X-Virus-Checked: Checked by ClamAV on apache.org On 11/27/12, Gary Martin wrote: > We should probably get a decision on this if it is going to be a starter > ticket for someone so that there are clear instructions about what is > wanted out of it. starter ticket if something like this will solve the issue .timeline img { width: ... } > I might also suggest changing the ticket title when it > is decided. > /me changing ... > There are a few complications for my decision here as I am hoping to > have truncated comments for events by default. On the other hand, I am > also interested in whether it would be worth providing a means to > expand/pop-up the full comment from truncated comments so this ticket > may still be relevant. > IMO we should render them using one-liner wiki formatters . If so images and macros should not be rendered -- Regards, Olemis. Blog ES: http://simelo-es.blogspot.com/ Blog EN: http://simelo-en.blogspot.com/ Featured article: