I have one question about when I call dangerouslySetInnerHTML, would cause line break.
If i replace them with spaces, it would work
please check my codesandbox
https://codesandbox.io/s/dangerouslysetinnerhtml-4u16s
Non-breaking space ( ) and a normal space () has different char code.
console.log(example.textContent[0].charCodeAt(0));
console.log(example.textContent[1].charCodeAt(0));
<div id="example"> </div>
When you connect words using , the browser will not break the connecting words because of its non-breakable property. Hence, the browser will parse it as if it is one long word.
Just like normal long word, browsers won't break the word unless you have word-break style set differently.
I believe the code below can further demonstrate the difference:
div {
width: 30px;
border: 1px solid black;
}
<div>I have a pen and I have an apple</div>
<div>IhaveapenandIhaveanapple</div>
<div>I have a pen and I have an apple</div>
Related
Constantly while testing, I get these extremely tall and hideous errors saying something like this: Warning: validateDOMNesting(...): <a> cannot appear as a descendant of <a>. They flood my console and make it hard to differentiate other errors that I actually care about.
These checks are apparently non-configurable (based on the pages and pages of closed issues asking for an option to change them) so I would just like to turn them off. As React does not accept feature requests, support requests or questions at all, I was directed to ask the question here instead. (Please correct me if Stack Overflow is not the right place to ask this)
My use-case for this is rendering a Markdown description inside of a clickable tile. Since the tile is clickable and leads to a different route, it is a link. But, since some descriptions also have links in them, React gets really mad and throws giant errors in console.
I have read an answer here that said nesting anchor elements is forbidden in HTML - in this case, I simply don't care, as that is literally what it means to allow links in Markdown rendered inside another link.
What about overlaying your link instead of wrapping it around the other HTML?
Something like:
.container {
position: relative;
}
.link {
position: absolute;
top: 0; right: 0; bottom: 0; left: 0;
transition: 1s background-color;
}
.link:hover {
background-color: rgba(0, 0, 200, 0.2);
}
<div class=container>
<a class=link href="goes-somewhere"></a>
<div class=markdown>
<h1>My markdown</h1>
<a class=some-other-link href="goes-somewhere-else">this one is in the document</a>
</div>
</div>
In my react app, I have a big piece of generated code (110k lines) to show on screen (an openapi json spec). I wrapped it in a <pre> tag with:
overflow-y: scroll;
word-wrap: break-word;
white-space: pre-wrap;
font-family: monospace;
height: 100%;
This <pre> has a parent <div> which set the height to something like 800px so it can scroll.
This used to work well, but recently chrome hang completely when displaying it. It works on Brave and Firefox without any issues. Strangely, the code is shared on server, if I type the url of the server and display the code directly (no react, just basic code display), chrome behave normally. It automatically wrap the code in a <pre> just like I do, with the same css style, except for the height:100%; I wonder what the hang in my application all of a sudden.
Thanks for any help.
Used react-virtualized list with chunks of data. Not ideal, but good enough for our purpose.
Is there a way to preserve line breaks from user input. At the moment I am just getting the user input sending it to mongoDb and returning that text. However if my input is :
"new
line",
my output would be "new line".
Can anyone suggest a fix?
Use css white-space for styling it.
.foo {
white-space: pre-line;
}
a small addition to #FELIXMOSH's correct answer: also use word-wrap because white-space property can cause overflowing sometimes. And apply this css to the element that will host the mongodb data.
anyClass {
white-space: pre-wrap;
word-wrap: break-word;
}
I am trying to create a responsive image wrap gallery. Each image will have a header. I distribute them using column-count of webkit.
The problem is this: I've specified a container to be "relative". Inside that container, I have an "absolute" header followed by an image. What seems to be happening in some values of column-count is that the header is going to another column and the image in the next. I need them both to be together at all times and I'm surprised why the absolute within relative container is not doing that.
A codepen for reference: http://codepen.io/pliablepixels/full/YwWLzy/
The core image gallery code is:(SO insists I include a code fragment when posting a codepen link, so here goes)
<div style="-webkit-column-count:{{ cols }};-webkit-column-gap:0px;line-height:0px;">
<span ng-repeat="image in images">
<div style="position:relative">
<div class="my_header">Header</div>
<img class="scaled_image" src={{ image.src }} />
</div>
</span>
</div>
Please change the column values and note the header behavior.
How does one solve this? (Note I must use an img tag - can't use background-image)
thanks
Columns
To protect elements from breaking and keep them entirely in a column you can add these properties:
.element {
-webkit-column-break-inside: avoid; /* Chrome, Safari, Opera */
page-break-inside: avoid; /* Firefox */
break-inside: avoid; /* IE 10+ */
}
Your fixed example http://codepen.io/anon/pen/rxMWxa
Header
Such behaviour occurs because you've added line-height:0px to your container div. So you can just return header's line-height value to normal. Fixed that in codepen.
Using line-height sometimes can make headache. Try to use padding like below:
.my_header {
background-color: red;
padding: 2px 4px;
line-height: normal;
}
So, this is an odd one...
I've got basic pagination code:
<div class="pagination">
< 1 <a class="current">2</a> 3 >
</div>
And I want it all centred, so I'm using inline-block on the anchor tags. Simple enough, stripped down CSS code:
.pagination{text-align:center; margin-bottom:20px;}
.pagination > a{display:inline-block; vertical-align:middle; margin:0 2px 0 1px;}
.ie7 .pagination > a{zoom:1;}
.pagination .next,
.pagination .prev{width:26px; height:38px; text-indent:-9999px; overflow:hidden;
background:url(../images/page-arrows.png) no-repeat;}
.pagination a{width:37px; height:31px; line-height:32px; font-size:15px; font-weight:bold; color:#7e7e7e;
background:url(../images/page-numbers.png) left top no-repeat;}
Problem is that, NOTHING is displaying in IE7 (at least IE7-mode of IE9). I'm well aware of the display-inline bugs that IE7 has, but those only apply to elements that aren't inline by default. I've added in a zoom:1 anyway though for good measure.
If I put a background colour on the .pagination wrapper, that wrapper does indeed show up with the background colour, but the elements inside just aren't showing!
I've tried the usual IE 'fixes' ...position:relative, zoom:1, height:1% on any and every element, but not luck.
What am I missing?!
After some experimenting in JSFiddle I've managed to discover that the problem relates to this particular rule
.pagination .prev {text-indent:-9999px; }
Disabling this fixes the issue but is not ideal as you would then have the text charecter appear on top of your background images.
Interestingly enough your .next does not cause the same issue. with that in mind added an to either side of your paging control (so your center alignment dosnt get skewed) and it seems to of fixed the problem.
<div class="pagination">
< 1 <a class="current">2</a> 3 >
</div>
JSFiddle available here (background images replaced with solid colors for obvious reasons)