Container queries are going to solve this long-standing issue in web design where we want to make design choices based on the size of an element (the container) rather than the size of the entire page. So, if a container is 600px wide, perhaps it has a row-like design, but any narrower than that it has a column-like design, and we’ll have that kind of control. That’s much different than transitioning between layouts based on screen size.
We can already size some things based on the size of an element, thanks to the % unit. For example, all these containers are 50% as wide as their parent container.
The % here is 1-to-1 with the property in use, so width is a % of width. Likewise, I could use % for font-size, but it will be a % of the parent container’s font-size. There is nothing that lets me cross properties and set the font-size as a % of a container’s width.
That is, unless we get container units! Here’s the table of units per the draft spec:
unit
relative to
qw
1% of a query container’s width
qh
1% of a query container’s height
qi
1% of a query container’s inline size
qb
1% of a query container’s block size
qmin
The smaller value of qi or qb
qmax
The larger value of qi or qb
With these, I could easily set the font-size to a percentage of the parent container’s width. Or line-height! Or gap! Or margin! Or whatever!
Miriam notes that we can actually play with these units right now in Chrome Canary, as long as the container queries flag is on.
I had a quick play too. I’ll just put a video here as that’ll be easier to see in these super early days.
And some great exploratory work from Scott here as well:
Ahmad Shadeed is also all over this!
Query units can save us effort and time when dealing with things like font-size, padding, and margin within a component. Instead of manually increasing the font size, we can use query units instead.
Imagine having to manually send an email to your subscribers every time you publish a post. Drafting up an email, gathering your subscriber list, and sending it to all of them wastes a lot of time you could spend working on your blog. Why do that when you can simply automate the process and have […]
I have a problem to do price data and i don’t know to insert it into the coding
this is question
this is the coding that i have made
<?php
$page_title = 'Yoho Express!';
include ('includes/header.html');
?>
<form action="q2.php" method="post">
<p><h1><fieldset><legend>Enter your information in the form below:</legend></p></h1>
<p><b>Departure day:</b>
<?php
//This programme is display in an array.
$day = array (1 =>'Select',
'Saturday',
'Sunday',
'Monday',
'Tuesday',
'Wednesday',
'Thursday',
'Friday');
//the programme is display using the pull-down menu.
echo '<select name="day">';
foreach ($day as $key => $value) {
echo "<option value=\"$value\">$value</option>\n";
}
echo '</select>';
?></p>
<p><b>Departure time:</b>
<?php
//This programme is display in an array.
$time = array (1=>'Select',
'7:00',
'10:00',
'13:00',
'16:00',
'21:00');
//the programme is display using the pull-down menu.
echo '<select name="time">';
foreach ($time as $key => $value) {
echo "<option value=\"$value\">$value</option>\n";
}
echo '</select>';
?>
</fieldset>
<b><p><div align="left"><input type="submit" name="submit" value="Book" /></div></b></p>
</form>
<?php
if($_SERVER['REQUEST_METHOD']=='POST'){
//handler
// Validate day
if (!empty($_POST['day'])) {
$day = $_POST['day'];
} else {
$day = NULL;
echo '<p><b><font color="purple">You forgot to enter your departure day!</b></p>';
}
// Validate time
if (!empty($_POST['time'])) {
$time = $_POST['time'];
} else {
$time = NULL;
echo'<p><b><font color="purple">You forgot to enter your departure time!</b></p>';
}
// Validate price
if (!empty($_POST['price'])) {
$price = $_POST['price'];
} else {
price= NULL;
}
// If everything is okay, print the message.
if ($day && $time && $price) {
// Print the submitted information.
echo "<b><font color='purple'>Below are your bus ticket details </font></b></p>
<br /><b>Day:</b>$day
<br /><b>Time:</b>$time
<br /><b>Price No:</b>$price";
} else {
// One form element was not filled out properly.
echo '<p><font color="red">Please go back and fill out the form again.</font></p>';
}
}
include('includes/footer.html');
?>
Geolocation tracking can be one of the most valuable features a website possesses. Finding out your visitors’ IP and geolocation can be indispensable, especially if you’re running an eCommerce business or any similar type of...
CSS ::before and ::after pseudo-elements allow you to insert “content” before and after any non-replaced element (e.g. they work on a <div> but not an <input>). This effectively allows you to show something on a web page that might not be present in the HTML content. You shouldn’t use it for actual content because it’s not very accessible in that you can’t even select and copy text inserted on the page this way — it’s just decorative content.
In this article, I’ll walk you through seven different examples that showcase how ::before and ::after can be used to create interesting effects.
Note that for most examples, I am only explaining the parts of the code that deal specifically with CSS pseudo-elements. That said, all of the CSS is available in the embedded demos if you want to see the code for additional styling.
Styling Broken images
When a user visits your website, their internet connection (or a factor beyond your control) might prevent your images from downloading and, as a result, the browser shows a broken image icon and and the image’s alt text (if it’s actually there).
How about showing a custom placeholder instead? You can pull this off using ::before and ::after with a bit of CSS positioning.
First, we need to use relative positioning on the image element. We are going to use absolute positioning on one of the pseudo-elements in a bit, so this relative position makes sure make sure the pseudo-element is positioned within the content of the image element, rather than falling completely out of the document flow.
img {
display: block; /* Avoid the space under the image caused by line height */
position: relative;
width: 100%
}
Next, let’s create the region of the broken image effect using the image’s ::before pseudo-element. We’re going to style this with a light gray background and slightly darker border to start.
<img> is a replaced element. Why are you using ::before pseudo-element on it? It wont work!. Correct. In this scenario the pseudo-element will show in Chrome and Firefox when the image fails to load, which is exactly what you want. Meanwhile, Safari only shows the styling applied to the alt text.
The styling is applied to the top-left corner of the broken image.
So far, so good. Now we can make it a block-level element (display: block) and give it a height that fills the entire available space.
We can refine the style a little more. For example, let’s round the corners. We should also give the alt text a little breathing room by giving the pseudo-element full width and absolute positioning for better control placing things where we want.
If you stopped here and checked your work, you might be scratching your head because the alt text is suddenly gone.
That’s because we set content to an empty string (which we need to display our generated content and styles) and cover the entire space, including the actual alt text. It’s there, we just can’t see it.
We can see it if we display the alt text in an alternate (get it?) way, this time with help form the ::after pseudo-element. The content property is actually capable of displaying the image’s alt attribute text using the attr() function:
A quick fix is to target the alt attribute directly using an attribute selector (in this case, img[alt]), and target similar styles there so things match up with Chrome.
Now we have a great placeholder that’s consistent in Chrome and Firefox.
Custom blockquote
Blockquotes are quotes or an excerpts from a cited work. They’re also provide a really great opportunity to break up a wall of text with something that’s visually interesting.
I want to look at another technique, one that incorporates ::before and ::after. Like we saw with the last example, we can use the content property to display generated content, and apply other properties to dress it up. Let’s put large quotation marks at the start and end of a blockquote.
The HTML is straightforward:
<blockquote>
<!-- Your text here -->
</blockquote>
Note the position: relative in there because, as you’ll learn, it’s essential for positioning the blockquotes.
As you’ve probably guessed, we’re going to use ::before for the first quotation mark, and ::after for the closing one. Now, we could simply call the content property on both and generate the marks in there. But, CSS has us covered with open-quote and close-quote values.
blockquote::before {
content: open-quote;
/* Place it at the top-left */
top: 0;
left: 0;
}
blockquote::after {
content: close-quote;
/* Place it at thee bottom-right */
bottom: 0;
right: 0;
}
This gets us the quotation marks we want, but allow me to button up the styles a bit:
We have ordered (<ol>) and unordered (<ul>) lists in HTML. Both have default styling dictated by the browser’s User Agent stylesheet. But with ::before pseudo-element, we can override those “default” styles with something of our own. And guess what? We can use emojis (😊) on the content property!
While this is great and all, it’s worth noting that we could actually reach for the ::marker pseudo-element, which is designed specifically for styling list markers. Eric Meyer shows us how that works and it’s probably a better way to go in the long run.
The customization is all thanks to modifications added to the <input> element via the ::before and ::after pseudo-elements. But first, here is some baseline CSS for the <form> element:
We’re going to “hide” the checkbox’s default appearance while making it take up the full amount of space. Weird, right? It’s invisible but still technically there. We do that by:
changing its position to absolute,
setting the appearance to none, and
setting its width and height to 100%.
input {
-webkit-appearance: none; /* Safari */
cursor: pointer; /* Show it's an interactive element */
height: 100%;
position: absolute;
width: 100%;
}
Now, let’s style the <input> element with its ::before pseudo-element. This styling will change the appearance of the input, bringing us closer to the final result.
input::before {
background: #fff;
border-radius: 50px;
content: "";
height: 70%;
position: absolute;
top: 50%;
transform: translate(7px, -50%); /* Move styling to the center of the element */
width: 85%;
}
Next, we need to create the “toggle” button and it just so happens we still have the ::after pseudo-element available to make it. But, there are two things worth mentioning:
The background is a linear-gradient.
The “toggle” button is moved to the center of the <input> with the transform property.
Try clicking on the toggle button. Nothing happens. That’s because we’re not actually changing the checked state of the <input>. And even if we were, the result is… unpleasant.
The fix is to apply the :checked attribute to the ::after pseudo-element of the <input>. By specifically targeting the checked state of the checkbox and chaining it to the ::after pseudo-element, we can move the toggle back into place.
We can decorate images with borders to make them stand out or fit more seamlessly within a design. Did you know we can use a gradient on a border? Well, we can with ::before (there are other ways, too, of course).
The core idea is to create a gradient over the image and use the CSS z-index property with a negative value. The negative value pulls the gradient below the image in the stacking order. This means the image always appears on top as long as the gradient has a negative z-index.
.gradient-border::before {
/* Renders the styles */
content: "";
/* Fills the entire space */
position: absolute;
top: 0;
left: 0;
bottom: 0;
right: 0;
/* Creates the gradient */
background-image: linear-gradient(#1a1a1a, #1560bd);
/* Stacks the gradient behind the image */
z-index: -1;
}
figure {
/* Removes the default margin */
margin: 0;
/* Squeezes the image, revealing the gradient behind it */
padding: 10px;
}
Gradient overlays
This is similar to what we did in the previous example, but here, we’re applying the gradient on top of the image. Why would we do that? It can be a nice way to add a little texture and depth to the image. Or perhaps it can be used to either lighten or darken an image if there’s text on top it that needs extra contrast for legibility.
While this is similar to what we just did, you’ll notice a few glaring differences:
See that? There’s no z-index because it’s OK for the gradient to stack on top of the image. We’re also introducing transparency in the background gradient, which lets the image bleed through the gradient. You know, like an overlay.
Custom radio buttons
Most, if not all, of us try to customize the default styles of HTML radio buttons, and that’s usually accomplished with ::before and ::after, like we did with the checkbox earlier.
We’re going to set a few base styles first, just to set the stage:
::before should be positioned at the top-left corner of the radio button, and when it’s checked, we change its background color.
.form-input::before {
/* Renders the styles */
content: '';
/* Shows that it's interactive */
cursor: pointer;
/* Positions it to the top-left corner of the input */
position: absolute;
top: 0;
left: 0;
/* Takes up the entire space */
height: 100%;
width: 100%;
}
/* When the input is in a checked state... */
.form-input:checked::before {
/* Change the background color */
background: #21209c;
}
We still need to iron a few things out using ::after. Specifically, when the radio button is checked, we want to change the color of the circular ring to white because, in its current state, the rings are blue.
.form-input::after {
/* Renders the styles */
content: '';
/* Shows that it's interactive */
cursor: pointer;
/* A little border styling */
border-radius: 50px;
border: 4px solid #21209c;
/* Positions the ring */
position: absolute;
left: 10%;
top: 50%;
transform: translate(0, -50%);
/* Sets the dimensions */
height: 15px;
width: 15px;
}
/* When the input is in a checked state... */
.form-input:checked::after {
/* Change ::after's border to white */
border: 4px solid #ffffff;
}
The form label is still unusable here. We need to target the form label directly to add color, and when the form input is checked, we change that color to something that’s visible.
Click the buttons, and still nothing happens. Here what’s going on. The position: absolute on ::before and ::after is covering things up when the radio buttons are checked, as anything that occurs in the HTML document hierarchy is covered up unless they are moved to a new location in the HTML document, or their position is altered with CSS. So, every time the radio button is checked, its label gets covered.
You probably already know how to fix this since we solved the same sort of thing earlier in another example? We apply z-index: 1 (or position: absolute) to the form label.
.form-label {
color: #21209c;
font-size: 1.1rem;
margin-left: 10px;
z-index: 1; /* Makes sure the label is stacked on top */
/* position: absolute; This is an alternative option */
}
Wrapping up
We covered seven different ways we can use the ::before and ::after pseudo-elements to create interesting effects, customize default styles, make useful placeholders, and add borders to images.
By no means did we cover all of the possibilities that we can unlock when we take advantage of these additional elements that can be selected with CSS. Lynn Fisher, however, has made a hobby out of it, making amazing designs with a single element. And let’s not forget Diana Smith’s CSS art that uses pseudo-elements in several places to get realistic, painting-like effects.
I'm currently studying a peneteration/hacking course. I am trying to use nmap against a target to find all the ports that are filtered.
I thought if I used an ACK-scan nmap would give me all the filtered ports. I used
nmap -sA -p- target
and the result was All the 65535 ports scanned are unfiltered. Is this even reasonable? What other scans can I use to complement my first scan?
WooCommerce is one of the most popular e-commerce plugins for WordPress with over 5 million active installations at the time of writing. The plugin helps you to convert a mere WordPress site into a powerful e-commerce platform perfect for any online store you have in mind. It ships with a ton of features including shop, product, […]
This post will explain why a database (DB) is tagged as a recovery pending. It will also discuss how to resolve the ‘SQL server database in recovery pending status' issue. You may fix the issue by running queries in SQL Server Management Studio (SSMS) or by utilizing a professional SQL database recovery tool.
Sendbird, a mobile communications services provider, has added a new FAQ chatbot to Sendbird Desk, the company’s platform for orchestrating embeddable live chat support. By leveraging this new product customers can offload quick questions to AI, freeing up live agents for more in-depth support.
ProgrammableWeb reached out to Sendbird to discuss what this means for developers.
Amongst many other great things, the Internet gave humanity the free movement of public information. With so much data available at one click of a button, third parties that build businesses and develop products have...
I'm having trouble in my assignment
Assignment :: TwoLargestElements
Complete the following program so that it computes and writes out the two largest elements in the array.
It always display "12" on both largest and largest2
import java.io.* ;
public class TwoLargest {
public static void main ( String[] args )
throws IOException {
int[] data = {3, 1, 5, 7, 4, 12, -3, 8, -2};
int largest = 0, largest2 = 0;
for ( int index = 0; index < data.length; index++)
if(largest < data[index]) {
largest = data [index];
}
for ( int index = 0; index < data.length; index++)
if (largest2 < largest) {
largest2 = largest;
}
System.out.println("The largest number in the array is: " + largest);
System.out.println("The second largest number in the array is: " + largest2);
}
}
(Jumble word program) (plz guys help me to make this program)
user enter few characters randomly, then press enter, (your program stores 50 names of your class fellows)
if by rearranging your entered characters it matches to the names stored,
then it will show it, otherwise it will show that name does not exist.
for example.... user enter llohe
correct name already declare (hello) program show this name