1
2
Theme development / Re: Click to expand quote
Last post by Arantor -The only way around this would be to assume that the end of a code block must start on a new line which will play hell with converters, not to mention making the code tag even more of a special case than it already is (and behave differently to everything else, e.g. quote where the end tag doesn’t have to be the only thing on the line)
3
Theme development / HTML main tag and a11y
Last post by Antechinus -Quote< header >, < main >, and < footer > must be direct children of < body > to be exposed to screen readers. They cannot be nested within other container elements.Which is a bit of a nuisance. With a forum it more or less means you either bung the news and linktree into < main >, or you find somewhere else for them.
I've gone with just bunging the news and linktree in. I figure that, in practice, the lower linktree and all sorts of minor shiznit (post buttons, etc, etc) are going to have to end up in there anyway, so no point getting too persnickety about the top linktree and the news being in there either. The skipnav link can still go straight to #main_content_section, so no dramas there.
Interesting, that blew right through the tag ... to investigate! Thanks for the report.
Test quoting my earlier post...
ETA: Seems to do what it says on the tin.
Now to try it with something else...
Ok, here's a bug for you. When I test post a code box containing regex*, it breaks at one of the code tags nested in the regex.
IOW, it can't recognise that anything inside a code tag is code, even if it's another BBC tag.
This may be a general Elk bug, not specifically a bug in handling nested quotes. Not sure yet. I grabbed this example regex at random, just noticed the result, and haven't yet done any further testing.
Admittedly this is a particularly nasty edge case. Not sure it is worth attempting a bulletproof fix. Check it out in the BBC editor mode to see what is happening.
*(example is from an updated phpBB > SMF/Elk converter I'm working on)
s
yep, switched to default and no more strange images
Hear, hear!
I haven't get involved in this for quite some times (may be because I am not sure how) but so far I can only see that the 2.0 development is doing great. Thank you all for keeping it up and moving to the right direction.
Slowly getting all the features in place. You will notice the schema org data in its fullest form only when viewing the first page of a topic.
If there are other features that have been requested and are not in place, don't hesitate to post a little nudge reminder
I've gone with just bunging the news and linktree in. I figure that, in practice, the lower linktree and all sorts of minor shiznit (post buttons, etc, etc) are going to have to end up in there anyway, so no point getting too persnickety about the top linktree and the news being in there either. The skipnav link can still go straight to #main_content_section, so no dramas there.
4
Theme development / Re: Click to expand quote
Last post by Spuds -5
Theme development / Re: Click to expand quote
Last post by Antechinus -Quote from: Antechinus - Ok, example:Quote from: Third reply* lol *Quote from: Second reply* the entire text of War & Peace here *
In this example (which accurately represents an average internet discussion) if the admin setting was 1 level of nested quotes, you would see this...Quote from: Third reply* lol *Quote from: Second reply* the entire text of War & Peace here *
If the admin setting was 2 level of nested quotes, you would see this...Quote from: Third reply* lol *Quote from: Second reply* the entire text of War & Peace here *
ETA: Seems to do what it says on the tin.

Quote from: Third reply* lol *Quote from: Second reply* the entire text of War & Peace here *Code: [Select]/*--- Quote tag variations. ---*/</e></CODE>~s',
'~<QUOTE author=\\"(.+?)\\" post_id=\\"(.+?)\\" time=\\"(.+?)\\" user_id=\\"(.+?)\\"><s>(.+?)</s>~s',
'~<QUOTE author=\\"(.+?)\\"><s>(.+?)</s>~s',
'~<QUOTE><s>\[quote]</s>~s',
'~<e>\[/quote]</e></QUOTE>~s',
/*--- Code boxes: first case is an odd one. ---*/
'~<CODE><s>\[code]</s><i>\\n</i>~s',
'~<CODE><s>\[code]</s>~s',
'~<e>\
/*--- List types: decimal, lower-alpha, upper-alpha, lower-roman, upper-roman... ---*/
'~<LIST type="(.+?)">(.+?)~s',
'~<LIST>\~s',
</e></LIST>~s',
'~<e>\
'~<LI>\[\*]~s',
'~</LI>~s',[/code]
Ok, here's a bug for you. When I test post a code box containing regex*, it breaks at one of the code tags nested in the regex.
IOW, it can't recognise that anything inside a code tag is code, even if it's another BBC tag.
This may be a general Elk bug, not specifically a bug in handling nested quotes. Not sure yet. I grabbed this example regex at random, just noticed the result, and haven't yet done any further testing.

Admittedly this is a particularly nasty edge case. Not sure it is worth attempting a bulletproof fix. Check it out in the BBC editor mode to see what is happening.

*(example is from an updated phpBB > SMF/Elk converter I'm working on)
6
Feature Discussion / Re: Video Embed's
Last post by Spuds -Quote from: radu81 - yep, switched to default and no more strange imagesOther than the videos
7
Feature Discussion / Re: Video Embed's
Last post by radu81 -8
Site Feedback / Re: EARLY Beta version of 2.0
Last post by Frenzie -9
Site Feedback / Re: EARLY Beta version of 2.0
Last post by ahrasis -10
Site Feedback / Re: EARLY Beta version of 2.0
Last post by Spuds -If there are other features that have been requested and are not in place, don't hesitate to post a little nudge reminder