A pesar de que tiene suficiente espacio a su alrededor para ser un elemento de bloque, no se convierte en un onebox.
Try rebuilding the HTML of the post once — that often fixes issues where links don’t onebox properly:
I think the spaces in front of it would make it an inline onebox and not a full one. I’m not sure I know a workaround. ![]()
Did that work for you?
@JammyDodger, 지금까지 시도해 본 모든 인스턴스(총 약 8개)에서 제가 확인한 결과는 그와 같습니다.
@janan_gagan, 저는 어디에도 TL4 권한이 없습니다… 만약 여러분 중 누군가가 /1에 있는 제 게시물의 HTML5 콘텐츠를 다시 빌드해 줄 수 있다면, 그것이 작동하는지 확인할 수 있을 것입니다. 그러나 aforementioned 내용에 따르면, 작동할 것이라고 생각하지 않습니다.
그동안, 현재 이것이 불가능해 보이므로 Contribute > Feature 게시물로 전환했습니다.
어쨌든 감사합니다.
Yes, there’s a specific logic in our markdown-it tokens that forces links to be considered inline oneboxes in cases that are not top level links (ie. not inside any list/blockquote/etc)
@renato, they can still oneboxify inside <details>, though. Seems especially strange to permit that, but not any other block element. What’s the rationale?
There’s no explicit rationale, it’s just that raw HTML is seen by markdown-it in a flat way, it doesn’t try to infer the nesting from tags being opened/closed.
Raw Html node
Top level onebox
Raw Html node
@renato, seems to me that, insofar as the CSS defines the element that encapsulates a URI as a block element, oneboxification should occur; I can’t think of any problematic edge cases.