Open caseydriscoll opened 10 years ago
In thinking about this, it seems like we might be able to handle this through CSS too, i.e. override the CSS for those elements where we don't want any special treatment.
We could certainly do this for
, and others.
Yep, thats a good point.
Some elements like lists may cause headaches, but maybe not if everything was inline.
You want me to give this a shot?
-- Casey Driscoll Sent with Airmail
On January 16, 2014 at 10:34:02 AM, Curtis Faith (notifications@github.com) wrote:
In thinking about this, it seems like we might be able to handle this through CSS too, i.e. override the CSS for those elements where we don't want any special treatment.
We could certainly do this for
, and others. — Reply to this email directly or view it on GitHub.
Yes Casey, let's try doing this through CSS first. Changing Snudown is a much larger project if we need it.
initial attempt deployed to bootstrap.lightnetb.org
Closing after review. Good enough for an initial effort as it solves the problem. Bugs can be created in tickets.
On list-item pages, two lines of the latest comment or two lines of the selftext are rendered. Right now its just the input text, showing the raw markdown.
We'd like to possibly render some select inline elements like , , and/or
Other tags like <h*>s,
, or , items that cannot be displayed in two lines of text, should still not be rendered.
Some tags, like