ASA-BI Webinars
- “Bayesian designs in oncology clinical trials”, Dr. Lili Zhao (July 25, 2017)
- “How the ICH E9 addendum around estimands may impact our clinical trials”, Dr. Frank Bretz (August 17, 2017)
- “Impact of model complexity on operating characteristics of adaptive dose-finding methods”, Dr. Alexia Iasonos (September 11th, 2017)
- “Phase I trials design with dose expansion cohort”, Dr. Jincheng Shen (October 17th, 2017)
- “Blinded ongoing aggregate safety evaluation (Blinded-OASE)”, Dr. Greg Ball and Dr. William Wang (November 8th, 2017)
- “Assessing covariate effects using Jeffrey’s-type prior in the Cox model in the presence of a monotone partial likelihood”, Dr. Jing Wu (December 6th, 2017)
- “Dose-escalation trials without monotonicity assumption: A weighted differential entropy approach”, Dr. Thomas Jaki (February 27th, 2018)
- “EMPA-REG Outcome® - A Cardiovascular Outcome Trial designed according to the FDA Guidance ‘Diabetes Mellitus– Evaluating Cardiovascular Risk in New Anti-diabetic Therapies to Treat Type 2 Diabetes’”, Dr. Stefan Hantel (April 5th, 2018)
- “A practical design for a dual-agent dose-escalation trial that incorporates pharmacokinetic data”, Dr. Amy Cotterill (April 24th, 2018)
- “The Future is Now, but Where Should We Focus?”, Dr. Haoda Fu (July 12th, 2018)
ASA-BI Statistics Webinar Series # 1
- Topic: Bayesian designs in oncology clinical trials
- Speaker: Dr. Lili Zhao, Research Assistant Professor, Biostatistics Department, University of Michigan, USA
- Abstract
- Date: July 25th, 2017
- Time: 9:00-10:00 EST (New York), including 10-minute Q&A
- Slides
ASA-BI Statistics Webinar Series # 2
- Topic: How the ICH E9 addendum around estimands may impact our clinical trials
- Speaker: Dr. Frank Bretz, Global Head, Statistical Methodology and Consulting Group, Novartis, Switzerland
- Abstract
- Date: August 17th, 2017
- Time: 9:00-10:00 EST (New York), including 10-minute Q&A
- Slides
ASA-BI Statistics Webinar Series # 3
- Topic: Impact of model complexity on operating characteristics of adaptive dose-finding methods
- Speakers: Dr. Alexia Iasonos, Associate Attending Biostatistician, Memorial Sloan Kettering Cancer Center and Dr. Nolan Wages, Associate Professor, University of Virginia, USA
- Abstract
- Date: September 11th, 2017
- Time: 9:00-10:00 EST (New York), including 10-minute Q&A
- Slides
ASA-BI Statistics Webinar Series # 4
- Topic: Phase I trials design with dose expansion cohort
- Speaker: Dr. Jincheng Shen, Assistant Professor, Department of Population Health Sciences, University of Utah, USA
- Abstract
- Date: October 17th, 2017
- Time: 9:00-10:00 EST (New York), including 10-minute Q&A
- Slides: Upon request
ASA-BI Statistics Webinar Series # 5
- Topic: Blinded ongoing aggregate safety evaluation (Blinded-OASE)
- Speaker: Dr. Greg Ball, Principal Statistician and Dr. William (Bill) Wang, Executive Director, Merck Pharmaceuticals, Inc.
- Abstract
- Date: November 8th, 2017
- Time: 9:00-10:00 EST (New York), including 10-minute Q&A
- Slides
ASA-BI Statistics Webinar Series # 6
- Topic: Assessing covariate effects using Jeffrey’s-type prior in the Cox model in the presence of a monotone partial likelihood
- Speaker: Dr. Jing Wu, Assistant Professor, University of Rhode Island, USA
- Abstract
- Date: December 6th, 2017
- Time: 9:00-10:00 EST (New York), including 10-minute Q&A
- Slides
ASA-BI Statistics Webinar Series # 7
- Topic: Dose-escalation trials without monotonicity assumption: A weighted differential entropy approach
- Speaker: Dr. Thomas Jaki, Professor of Statistics, Lancaster University, UK
- Abstract
- Date: February 27th, 2018
- Time: 9:00-10:00 EST (New York), including 10-minute Q&A
- Slides
ASA-BI Statistics Webinar Series # 8
- Topic: EMPA-REG Outcome® - A Cardiovascular Outcome Trial designed according to the FDA Guidance “Diabetes Mellitus– Evaluating Cardiovascular Risk in New Anti-diabetic Therapies to Treat Type 2 Diabetes”
- Speaker: Dr. Stefan Hantel, Therapeutic Area Statistician, Boehringer Ingelheim, Germany
- Abstract
- Date: April 5th, 2018
- Time: 9:00-10:00 EST (New York), including 10-minute Q&A
ASA-BI Statistics Webinar Series # 9
- Topic: A practical design for a dual-agent dose-escalation trial that incorporates pharmacokinetic data
- Speaker: Dr. Amy Cotterill, Senior Statistician, Cancer Research UK Clinical Trials Unit, University of Birmingham, UK
- Abstract
- Date: April 24th, 2018
- Time: 9:00-10:00 EST (New York), including 10-minute Q&A
ASA-BI Statistics Webinar Series # 11
- Topic: The Future is Now, but Where We Should Focus
- Speaker: Dr. Haoda Fu, Research Advisor at Eli Lilly and Company and Adjunct Professor in Biostatistics at Indiana University School of Medicine
- Abstract
- Date: July 12th, 2018
- Time: 9:00-10:00 EST (New York), including 10-minute Q&A


Thier was something it should flkdafhjdfhdfd mljdjfj ijgoiuf pdjdhgousdupodpiug pj oibsdglks.
Thier was something it should flkdafhjdfhdfd mljdjfj ijgoiuf pdjdhgousdupodpiug pj oibsdglks.
Thier was something it should flkdafhjdfhdfd mljdjfj ijgoiuf pdjdhgousdupodpiug pj oibsdglks.
Thier was something it should flkdafhjdfhdfd mljdjfj ijgoiuf pdjdhgousdupodpiug pj oibsdglks.
Thier was something it should flkdafhjdfhdfd mljdjfj ijgoiuf pdjdhgousdupodpiug pj oibsdglks.


1. Introduction
This module describes CSS properties which enable authors to style user interface related properties and values.
Section 2.1 of CSS1 [CSS1] and Chapter 18 of CSS2 [CSS2] introduced several user interface related properties and values. User Interface for CSS3 (16 February 2000) introduced several new user interface related features.
This Working Draft incorporates, extends, and supersedes them.
1.1. Purpose
The purpose of this specification is to achieve the following objectives:
- Extend the user interface features in CSS2.1.
- Provide additional CSS mechanisms to augment or replace other dynamic presentation related features in HTML.
- Introduce directional navigation properties to assist in the construction of user interfaces which make use of a directional navigation model.
2. Module Interactions
This document defines new features not present in earlier specifications. In addition, it replaces and supersedes the following:
- Section 18.1, section 18.4, and Information on the stacking of outlines defined in Appendix E of Cascading Style Sheets, level 2, revision 1 [CSS21]
- User Interface for CSS3 (16 February 2000) [CSSUI]
3. Box Model addition
3.1. box-sizing property
- content-box
- This is the behavior of width and height as specified by CSS2.1. The specified width and height (and respective min/max properties) apply to the width and height respectively of the content box of the element. The padding and border of the element are laid out and drawn outside the specified width and height.
- border-box
- Length and percentages values for width and height (and respective min/max properties)
on this element determine the border box of the element.
That is, any padding or border specified on the element
is laid out and drawn inside this specified width and height.
The content width and height are calculated
by subtracting the border and padding widths of the respective sides
from the specified width
and height properties.
As the content width and height
cannot be negative ([CSS21], section 10.2),
this computation is floored at 0.
Used values, as exposed for instance through getComputedStyle(), also refer to the border box.
Note: This is the behavior of width and height as commonly implemented by legacy HTML user agents for replaced elements and input elements.
Note: In contrast to the length and percentage values, the auto value of the width and height properties (as well as other keyword values introduced by later specifications, unless otherwise specified) is not influenced by the box-sizing property, and always sets the size of the content box.
The following terms, whose definitions vary based on the computed value of box-sizing are introduced:
| box-sizing: content-box | box-sizing: border-box | |
|---|---|---|
| min inner width | min-width | max(0, min-width − padding-left − padding-right − border-left-width − border-right-width) |
| max inner width | max-width | max(0, max-width − padding-left − padding-right − border-left-width − border-right-width) |
| min inner height | min-height | max(0, min-height − padding-top − padding-bottom − border-top-width − border-bottom-width) |
| max inner height | max-height | max(0, max-height − padding-top − padding-bottom − border-top-width − border-bottom-width) |
The Visual formatting model details of [CSS21] are written assuming box-sizing: content-box. The following disambiguations are made to clarify the behavior for all values of box-sizing:
- In 10.3.3, the second
width
in the following phrase is to be interpreted as content width:If width is not auto and border-left-width + padding-left + width + [...]
- In 10.3.7,
width
is to be interpreted as content width in the following equation:left + margin-left + border-left-width + padding-left + width + [...]
- In 10.4,
width
,height
,min-width
,max-width
,min-height
andmax-height
are respectively to be interpreted as content width, content height, min inner width, max inner width, min inner height and max inner height in the following phrases:The tentative used width is calculated [...]
If the tentative used width is greater than max-width, the rules above are applied again, but this time using the computed value of max-width as the computed value for width.
If the resulting width is smaller than min-width, the rules above are applied again, but this time using the value of min-width as the computed value for width.
Select from the table the resolved height and width values for the appropriate constraint violation. Take the max-width and max-height as max(min, max) so that min ≤ max holds true. In this table w and h stand for the results of the width and height computations [...]
- All instances of these words in the table
Then apply the rules under "Calculating widths and margins" above, as if width were computed as this value.
- In 10.6.4,
height
is to be interpreted as content height in the following equation:top + margin-top + border-top-width + padding-top + height + [...]
- In 10.7,
width
,height
,min-height
andmax-height
are respectively to be interpreted as content width, content height, min inner height and max inner height in the following phrases:The tentative used height is calculated [...]
If this tentative height is greater than max-height, the rules above are applied again, but this time using the value of max-height as the computed value for height.
If the resulting height is smaller than min-height, the rules above are applied again, but this time using the value of min-height as the computed value for height.
[...] use the algorithm under Minimum and maximum widths above to find the used width and height. Then apply the rules under "Computing heights and margins" above, using the resulting width and height as if they were the computed values.
Using box-sizing to evenly share space
This example uses box-sizing to evenly horizontally split two divs with fixed size borders inside a div container, which would otherwise require additional markup.
sample CSS:
div.container {
width:38em;
border:1em solid black;
}
div.split {
box-sizing:border-box;
width:50%;
border:1em silver ridge;
float:left;
}
sample HTML fragment:

This div occupies the left half.

This div occupies the right half.

demonstration of sample CSS and HTML:
4. Outline properties
At times, style sheet authors may want to create outlines around visual objects such as buttons, active form fields, image maps, etc., to make them stand out. Outlines differ from borders in the following ways:
- Outlines do not take up space.
- Outlines may be non-rectangular.
- UAs often render outlines on elements in the :focus state.
The outline properties control the style of these dynamic outlines.
The stacking of the rendering of these outlines is explicitly left up to implementations to provide a better user experience per platform. This supersedes the stacking of outlines as defined in CSS 2.1.
Keyboard users, in particular people with disabilities who may not be able to interact with the page in any other fashion, depend on the outline being visible on elements in the :focus state, thus authors must not make the outline invisible on such elements without making sure an alternative highlighting mechanism is provided.
The rendering of applying transforms to outlines is left explicitly undefined in CSS3-UI.
4.1. outline property
| Name: | outline |
|---|---|
| Value: | [ <outline-color> || <outline-style> || <outline-width> ] |
| Initial: | see individual properties |
| Applies to: | all elements |
| Inherited: | no |
| Percentages: | N/A |
| Media: | visual |
| Computed value: | see individual properties |
| Animatable: | see individual properties |
4.2. outline-width property
| Name: | outline-width |
|---|---|
| Value: | <‘border-width’> |
| Initial: | medium |
| Applies to: | all elements |
| Inherited: | no |
| Percentages: | N/A |
| Media: | visual |
| Computed value: | absolute length; 0 if the outline style is none. |
| Animatable: | as length |
4.3. outline-style property
| Name: | outline-style |
|---|---|
| Value: | auto | <‘border-style’> |
| Initial: | none |
| Applies to: | all elements |
| Inherited: | no |
| Percentages: | N/A |
| Media: | visual |
| Computed value: | specified value |
| Animatable: | no |
4.4. outline-color property
| Name: | outline-color |
|---|---|
| Value: | <color> | invert |
| Initial: | invert |
| Applies to: | all elements |
| Inherited: | no |
| Percentages: | N/A |
| Media: | visual |
| Computed value: | The computed value for invert is invert. For <color> values, the computed value is as defined for the [CSS3COLOR] color property. |
| Animatable: | as color |
The outline created with the outline properties is drawn "over" a box, i.e., the outline is always on top, and doesn’t influence the position or size of the box, or of any other boxes. Therefore, displaying or suppressing outlines does not cause reflow.
Outlines may be non-rectangular. For example, if the element is broken across several lines, the outline should be an outline or minimum set of outlines that encloses all the element’s boxes.
Each part of the outline should be fully connected rather than open on some sides (as borders on inline elements are when lines are broken).
The parts of the outline are not required to be rectangular. To the extent that the outline follows the border edge, it should follow the border-radius curve.
The position of the outline may be affected by descendant boxes.
User agents should use an algorithm for determining the outline that encloses a region appropriate for conveying the concept of focus to the user.
Note: This specification does not define the exact position or shape of the outline, but it is typically drawn immediately outside the border box.
The outline-width property accepts the same values as border-width ([CSS3BG], Section 4.3).
The outline-style property accepts the same values as border-style ([CSS3BG], Section 4.2), except that hidden is not a legal outline style. In addition, in CSS3, outline-style accepts the value auto. The auto value permits the user agent to render a custom outline style, typically a style which is either a user interface default for the platform, or perhaps a style that is richer than can be described in detail in CSS, e.g. a rounded edge outline with semi-translucent outer pixels that appears to glow. As such, this specification does not define how the outline-color is incorporated or used (if at all) when rendering auto style outlines. User agents may treat auto as solid.
The outline-color property accepts all colors, as well as the keyword invert. Invert is expected to perform a color inversion on the pixels on the screen. This is a common trick to ensure the focus border is visible, regardless of color background.
Conformant UAs may ignore the invert value on platforms that do not support color inversion of the pixels on the screen.
If the UA does not support the invert value then it must reject that value at parse-time, and the initial value of the outline-color property is the currentColor [CSS3COLOR] keyword.
The outline property is a shorthand property, and sets all three of outline-style, outline-width, and outline-color.
Note: The outline is the same on all sides. In contrast to borders, there are no outline-top or outline-left etc. properties.
This specification does not define how multiple overlapping outlines are drawn, or how outlines are drawn for boxes that are partially obscured behind other elements.
Here’s an example of drawing a thick outline around a BUTTON element:
button { outline: thick solid }
Graphical user interfaces may use outlines around elements to tell the user which element on the page has the focus. These outlines are in addition to any borders, and switching outlines on and off should not cause the document to reflow. The focus is the subject of user interaction in a document (e.g., for entering text, selecting a button, etc.).
For example, to draw a thick black line around an element when it has the focus, and a thick red line when it is active, the following rules can be used:
:focus { outline: thick solid black }
:active { outline: thick solid red }
Note: Since the outline does not affect formatting (i.e., no space is left for it in the box model), it may well overlap other elements on the page.
4.5. outline-offset property
By default, the outline is drawn starting just outside the border edge. However, it is possible to offset the outline and draw it beyond the border edge.
| Name: | outline-offset |
|---|---|
| Value: | <length> |
| Initial: | 0 |
| Applies to: | all elements |
| Inherited: | no |
| Percentages: | N/A |
| Media: | visual |
| Computed value: | <length> value in absolute units (px or physical). |
| Animatable: | as length |
If the computed value of outline-offset is anything other than 0, then the outline is outset from the border edge by that amount.
For example, to leave 2 pixels of space between a focus outline and the element that has the focus or is active, the following rule can be used:
:focus,:active { outline-offset: 2px }
Negative values must cause the outline to shrink into the border box. Both the height and the width of outside of the shape drawn by the outline must not become smaller than twice the computed value of the outline-width property, to make sure that an outline can be rendered even with large negative values. User Agents must apply this constraint independently in each dimension. If the outline is drawn as multiple disconnected shapes, this constraint applies to each shape separately.
Note: Negative value constraints are an at risk feature due to interoperability problems, and thus might be dropped from a must to a should.
5. Resizing & Overflow
CSS2.1 provides a mechanism for controlling the appearance of a scrolling mechanism (e.g. scrollbars) on block container elements. This specification adds to that a mechanism for controlling user resizability of elements as well as the ability to specify text overflow behavior.
5.1. resize property
The resize property allows the author to specify whether or not an element is resizable by the user, and if so, along which axis/axes.
| Name: | resize |
|---|---|
| Value: | none | both | horizontal | vertical |
| Initial: | none |
| Applies to: | elements with overflow other than visible |
| Inherited: | no |
| Percentages: | N/A |
| Media: | visual |
| Computed value: | specified value. |
| Animatable: | no |
- none
- The UA does not present a resizing mechanism on the element, and the user is given no direct manipulation mechanism to resize the element.
- both
- The UA presents a bidirectional resizing mechanism to allow the user to adjust both the height and the width of the element.
- horizontal
- The UA presents a unidirectional horizontal resizing mechanism to allow the user to adjust only the width of the element.
- vertical
- The UA presents a unidirectional vertical resizing mechanism to allow the user to adjust only the height of the element.
Currently it is possible to control the appearance of the scrolling mechanism (if any)
on an element using the overflow property
(e.g. overflow: scroll
vs. overflow: hidden
etc.).
The purpose of the resize property
is to also allow control over the appearance and function of the resizing mechanism
(e.g. a resize box or widget) on the element.
Note: The resizing mechanism is NOT the same as the scrolling mechanism. The scrolling mechanism allows the user to determine which portion of the contents of an element is shown. The resizing mechanism allows the user to determine the size of the element.
The resize property applies to elements whose computed overflow value is something other than visible.
The effect of the resize property on generated content is undefined. Implementations should not apply the resize property to generated content.
Note: the resize property may apply to generated content in the future if there is implementation of Interface CSSPseudoElement.
When an element is resized by the user, the user agent sets the width and height properties to px unit length values of the size indicated by the user, in the element’s style attribute DOM, replacing existing property declaration(s) if any, without !important if any.
If an element is resized in only one dimension, only the corresponding property is set, not both.
The precise direction of resizing (i.e. altering the top left of the element or altering the bottom right) may depend on a number of CSS layout factors including whether the element is absolutely positioned, whether it is positioned using the right and bottom properties, whether the language of the element is right-to-left etc. The UA should consider the direction of resizing (as determined by CSS layout), as well as platform conventions and constraints when deciding how to convey the resizing mechanism to the user.
The user agent must allow the user to resize the element with no other constraints than what is imposed by min-width, max-width, min-height, and max-height. (The "must" is at risk since only Firefox currently supports this, and may be downgraded to a "should").
Note: There may be situations where user attempts to resize an element to appear to be overriden or ignored, e.g. because of !important cascading declarations that supersede that element’s style attribute width and height properties in the DOM.
Changes to the computed value of an element’s resize property do not reset changes to the style attribute made due to user resizing of that element.
For example, to make iframes scrollable and resizable, the following rule can be used:
iframe,object[type^="text/"],
object[type$="+xml"],object[type="application/xml"]
{
overflow:auto;
resize:both;
}
5.2. Overflow Ellipsis: the text-overflow property
| Name: | text-overflow |
|---|---|
| Value: | [ clip | ellipsis | <string> ]{1,2} |
| Initial: | clip |
| Applies to: | block containers |
| Inherited: | no |
| Percentages: | N/A |
| Media: | visual |
| Computed value: | as specified |
| Animatable: | no |
This property specifies rendering when inline content overflows its line box edge in the inline progression direction of its block container element ("the block") that has overflow other than visible.
Text can overflow for example when it is prevented from wrapping
(e.g. due to white-space: nowrap
or a single word is too long to fit).
Values have the following meanings:
- clip
- Clip inline content that overflows its block container element. Characters may be only partially rendered.
- ellipsis
- Render an ellipsis character (U+2026) to represent clipped inline content. Implementations may substitute a more language, script, or writing-mode appropriate ellipsis character, or three dots "..." if the ellipsis character is unavailable.
- <string>
- Render the given string to represent clipped inline content. The given string is treated as an independent paragraph for bidi purposes.
Note: The <string> value, and the 2-value syntax "{1,2}" and functionality are all at risk.
The term "character" is used in this property definition for better readability and means "grapheme cluster" [UAX29] for implementation purposes.
If there is one value, it applies only to the end line box edge. If there are two values, the first value applies to the line-left edge, and the second value applies to the line-right edge. The terms end, line-left and line-right are defined in [CSS3-WRITING-MODES].
Note: the use of line-left and line-right rather than start and end when there are two values is intentional, to facilitate the use of directional characters such as arrows.
For the ellipsis and string values, implementations must hide characters and atomic inline-level elements at the applicable edge(s) of the line as necessary to fit the ellipsis/string. Place the ellipsis/string immediately adjacent to the applicable edge(s) of the remaining inline content. The first character or atomic inline-level element on a line must be clipped rather than ellipsed.
ellipsing details
- Ellipsing only affects rendering and must not affect layout nor dispatching of pointer events.
- The ellipsis is styled and baseline-aligned according to the block.
- Ellipsing occurs after relative positioning and other graphical transformations.
- If there is insufficient space for the ellipsis, then clip the rendering of the ellipsis itself (on the same side that neutral characters on the line would have otherwise been clipped with the text-overflow:clip value).
user interaction with ellipsis
- When the user is interacting with content (e.g. editing, selecting, scrolling), the user agent may treat text-overflow ellipsis or string values as text-overflow:clip.
- Selecting the ellipsis should select the ellipsed text. If all of the ellipsed text is selected, UAs should show selection of the ellipsis. Behavior of partially-selected ellipsed text is up to the UA.
text-overflow examples
These examples demonstrate setting the text-overflow of a block container element that has text which overflows its dimensions:
sample CSS for a div:
div { font-family:Helvetica,sans-serif; line-height:1.1;
width:3.1em; padding:.2em; border:solid .1em black; margin:1em 0;
}
sample HTML fragments, renderings, and your browser:
| HTML | sample rendering | your browser |
|---|---|---|
|
CSS IS AWESOME, YES
| |
| ||
| ||
|
Note: the side of the line that the ellipsis is placed depends on the direction of the block.
E.g. an overflow hidden right-to-left
(direction: rtl
)
block clips inline content on the left side,
thus would place a text-overflow ellipsis on the left
to represent that clipped content.
ellipsis interaction with scrolling interfaces
This section applies to elements with text-overflow other than text-overflow:clip (non-clip text-overflow) and overflow:scroll.
When an element with non-clip text-overflow has overflow of scroll in the inline progression dimension of the text, and the browser provides a mechanism for scrolling (e.g. a scrollbar on the element, or a touch interface to swipe-scroll, etc.), there are additional implementation details that provide a better user experience:
When an element is scrolled (e.g. by the user, DOM manipulation), more of the element’s content is shown. The value of text-overflow should not affect whether more of the element’s content is shown or not. If a non-clip text-overflow is set, then as more content is scrolled into view, implementations should show whatever additional content fits, only truncating content which would otherwise be clipped (or is necessary to make room for the ellipsis/string), until the element is scrolled far enough to display the edge of the content at which point that content should be displayed rather than an ellipsis/string.
This example uses text-overflow on an element with overflow scroll to demonstrate the above described behavior.
sample CSS:
div.crawlbar {
text-overflow: ellipsis;
height: 2em;
overflow: scroll;
white-space: nowrap;
width: 15em;
border:1em solid black;
}
sample HTML fragment:

CSS is awesome, especially when you can scroll
to see extra text instead of just
having it overlap other text by default.

demonstration of sample CSS and HTML:
As some content is scrolled into view, it is likely that other content may scroll out of view on the other side. If that content’s block container element is the same that’s doing the scrolling, and the computed value of text-overflow has two values, with the value applying to the start edge being a non-clip value, then implementations must render an ellipsis/string in place of the clipped content, with the same details as described in the value definition above, except that the ellipsis/string is drawn in the start (rather than end) of the block’s direction (per the direction property).
While the content is being scrolled, implementations may adjust their rendering of ellipses/strings (e.g. align to the box edges rather than line edges).
Same as previous example except with text-overflow: ellipsis ellipsis
, demonstrated:
If there is insufficient space for both start and end ellipses/strings, then only the end ellipsis/string should be rendered.
6. Pointing Devices and Keyboards
6.1. Pointer interaction
6.1.1. cursor property
| Name: | cursor |
|---|---|
| Value: |
[ [<url> [<x> <y>]?,]* [ auto | default | none | context-menu | help | pointer | progress | wait | cell | crosshair | text | vertical-text | alias | copy | move | no-drop | not-allowed | grab | grabbing | e-resize | n-resize | ne-resize | nw-resize | s-resize | se-resize | sw-resize | w-resize | ew-resize | ns-resize | nesw-resize | nwse-resize | col-resize | row-resize | all-scroll | zoom-in | zoom-out ] ] |
| Initial: | auto |
| Applies to: | all elements |
| Inherited: | yes |
| Percentages: | N/A |
| Media: | visual, interactive |
| Computed value: | as specified, except with any relative URLs converted to absolute |
| Animatable: | no |
This property specifies the type of cursor to be displayed for the pointing device when within the element’s border edge.
Note: As per [CSS3-BACKGROUND], the border edge is affected by border-radius.
User agents may ignore the cursor property over native user-agent controls such as scrollbars, resizers, or other native UI widgets e.g. those that may be used inside some user agent specific implementations of form elements.
Values have the following meanings:
- image cursors
-
- <url>
- The user agent retrieves the cursor from the resource designated by the URI.
If the user agent cannot handle the first cursor of a list of cursors,
it must attempt to handle the second, etc.
If the user agent cannot handle any user-defined cursor,
it must use the cursor keyword at the end of the list.
Conforming User Agents may, instead of <url>, support <image> which is a superset.
The UA must support the following image file formats:
- PNG, as defined in [PNG]
- SVG, as defined in [SVG], in secure static mode [SVG-INTEGRATION]
- any other non-animated image file format that they support for <image> in other properties, such as the the background-image property
In addition, the UA should support the following image file formats:
- SVG, as defined in [SVG], in secure animated mode [SVG-INTEGRATION]
- any other animated image file format that they support for <image> in other properties, such as the the background-image property
The UA may also support additional file formats.
Note: At the time of writing this specification (spring 2015), the only file formats supported for cursors in common desktop browsers are the .ico and .cur file formats, as designed by Microsoft. For compatibility with legacy content, UAs are encouraged to support these, even though the lack of an open specification makes it impossible to have a normative requirement about these formats. Some information on these formats can be found on Wikipedia.
The default object size for cursor images is a UA-defined size that should be based on the size of a typical cursor on the UA’s operating system.
The concrete object size is determined using the default sizing algorithm. If an operating system is incapable of rendering a cursor above a given size, cursors larger than that size must be shrunk to within the OS-supported size bounds, while maintaining the cursor image’s intrinsic ratio, if any.
The optional <x> and <y> coordinates identify the exact position within the image which is the pointer position (i.e., the hotspot).
- <x>
- <y>
-
Each is a <number>.
The x-coordinate and y-coordinate of the position
in the cursor’s coordinate system (left/top relative)
which represents the precise position that is being pointed to.
Note: This specification does not define how the coordinate systems of the various types of <image> are established, and defers these definitions to [CSS4-IMAGES].
If the values are unspecified, then the intrinsic hotspot defined inside the image resource itself is used. If both the values are unspecific and the referenced cursor has no defined hotspot, the effect is as if a value of "0 0" were specified.
If the coordinates of the hotspot, as specified either inside the image resource or by <x> and <y> values, fall outside of the cursor image, they must be clamped (independently) to fit.
- general purpose cursors
-
- auto
- The UA determines the cursor to display based on the current context, specifically: auto behaves as text over text, and default otherwise.
- default
- The platform-dependent default cursor. Often rendered as an arrow.
- none
- No cursor is rendered for the element.
- links and status cursors
-
- context-menu
- A context menu is available for the object under the cursor. Often rendered as an arrow with a small menu-like graphic next to it.
- help
- Help is available for the object under the cursor. Often rendered as a question mark or a balloon.
- pointer
- The cursor is a pointer that indicates a link.
- progress
- A progress indicator. The program is performing some processing, but is different from wait in that the user may still interact with the program. Often rendered as a spinning beach ball, or an arrow with a watch or hourglass.
- wait
- Indicates that the program is busy and the user should wait. Often rendered as a watch or hourglass.
- selection cursors
-
- cell
- Indicates that a cell or set of cells may be selected. Often rendered as a thick plus-sign with a dot in the middle.
- crosshair
- A simple crosshair (e.g., short line segments resembling a "+" sign). Often used to indicate a two dimensional bitmap selection mode.
- text
- Indicates text that may be selected. Often rendered as a vertical I-beam. User agents may automatically display a horizontal I-beam/cursor (e.g. same as the vertical-text keyword) for vertical text, or for that matter, any angle of I-beam/cursor for text that is rendered at any particular angle.
- vertical-text
- Indicates vertical-text that may be selected. Often rendered as a horizontal I-beam.
- drag and drop cursors
-
- alias
- Indicates an alias of/shortcut to something is to be created. Often rendered as an arrow with a small curved arrow next to it.
- copy
- Indicates something is to be copied. Often rendered as an arrow with a small plus sign next to it.
- move
- Indicates something is to be moved.
- no-drop
- Indicates that the dragged item cannot be dropped at the current cursor location. Often rendered as a hand or pointer with a small circle with a line through it.
- not-allowed
- Indicates that the requested action will not be carried out. Often rendered as a circle with a line through it.
- grab
- Indicates that something can be grabbed (dragged to be moved). Often rendered as the backside of an open hand.
- grabbing
- Indicates that something is being grabbed (dragged to be moved). Often rendered as the backside of a hand with fingers closed mostly out of view.
- resizing and scrolling cursors
-
- e-resize, n-resize, ne-resize, nw-resize, s-resize, se-resize, sw-resize, w-resize
- Indicates that some edge is to be moved. For example, the se-resize cursor is used when the movement starts from the south-east corner of the box.
- ew-resize, ns-resize, nesw-resize, nwse-resize
- Indicates a bidirectional resize cursor.
- col-resize
- Indicates that the item/column can be resized horizontally. Often rendered as arrows pointing left and right with a vertical bar separating them.
- row-resize
- Indicates that the item/row can be resized vertically. Often rendered as arrows pointing up and down with a horizontal bar separating them.
- all-scroll
- Indicates that the something can be scrolled in any direction. Often rendered as arrows pointing up, down, left, and right with a dot in the middle.
- zooming cursors
-
- zoom-in, zoom-out
- Indicates that something can be zoomed (magnified) in or out, and often rendered as a magnifying glass with a "+" or "-" in the center of the glass, for zoom-in and zoom-out respectively.
Example: cursor fallback
Here is an example of using several cursor values.
:link,:visited {
cursor: url(example.svg#linkcursor),
url(hyper.cur),
url(hyper.png) 2 3,
pointer
}
This example sets the cursor on all hyperlinks (whether visited or not) to an external SVG cursor ([SVG10], section 16.8.3). User agents that don’t support SVG cursors would simply skip to the next value and attempt to use the "hyper.cur" cursor. If that cursor format was also not supported, the UA could attempt to use the "hyper.png" cursor with the explicit hot spot. Finally if the UA does not support any of those image cursor formats, the UA would skip to the last value and render the pointer cursor.
<IP_ADDRESS>. Cursor of the canvas
The document canvas is the infinite surface over which the document is rendered [CSS21]. Since no element corresponds to the canvas, in order to allow styling of the cursor when not over any element, the canvas cursor re-uses the root element’s cursor. However, if no boxes are generated for the root element (for example, if the root element has display: none), then the canvas cursor is the platform-dependent default cursor.
Note: An element might be invisible, but still generate boxes. For example, if the element has visibility: hidden but not display: none, boxes are generated for it and its cursor is used for the canvas.
6.2. Insertion caret
6.2.1. Coloring the insertion caret: caret-color
| Name: | caret-color |
|---|---|
| Value: | auto | <color> |
| Initial: | auto |
| Applies to: | elements that accept input |
| Inherited: | yes |
| Percentages: | N/A |
| Media: | interactive |
| Computed value: | The computed value for auto is auto. For <color> values, the computed value is as defined for the [CSS3COLOR] color property. |
| Animatable: | as color |
- auto
- User agents should use currentColor. User agents may automatically adjust the color of caret to ensure good visibility and contrast with the surrounding content, possibly based on the currentColor, background, shadows, etc.
- <color>
- The insertion caret is colored with the specified color.
The caret is a visible indicator of the insertion point in an element where text (and potentially other content) is inserted by the user. This property controls the color of that visible indicator.
Note: caret shape and blinking is outside the scope of this feature and thus unspecified.
Note: The caret-color property is at risk.
6.3. Keyboard control
6.3.1. Directional focus navigation: the nav-up, nav-right, nav-down, nav-left properties
- auto
- The user agent automatically determines which element to navigate the focus to in response to directional navigational input.
- <id>
-
The <id> value is an ID selector [SELECT]. In response to directional navigation input corresponding to the property, the focus is navigated to the first element in tree order matching the selector.
If this refers to the currently focused element, the directional navigation input respective to the nav- property is ignored — there is no need to refocus the same element.
If no element matches the selector, the user agent automatically determines which element to navigate the focus to.
If the focus is navigated to an element that was not otherwise focusable, it becomes focusable only as the result of this directional navigation, and the :focus pseudo-class matches the element while it is focused as such.
Note: there were other options under consideration for such "not otherwise focusable" elements, including focus to the next otherwise focusable element in the document tree (including descendants of such a not otherwise focusable element). Input on such other options is welcome and explicitly solicited, especially from implementation experiences and author experience using the directional navigation properties in their content.
- <target-name>
- The <target-name> parameter indicates the target frame for the focus navigation. It is a <string> and it MUST NOT start with the underscore "_" character. Error handling: if it does start with an underscore, "_parent" navigates to the parent frame, "_root" is treated as root, and other values navigate to a frame by that name if it exists. If the specified target frame does not exist, the parameter will be treated as the keyword current, which means to simply use the frame that the element is in. The keyword root indicates that the user agent should target the full window.
User agents for devices with directional navigation keys respond by navigating the focus according to four respective nav-* directional navigation properties (nav-up, nav-right, nav-down, nav-left). This specification does not define which keys of a device are directional navigational keys.
Note: Typical personal computers have keyboards with four arrow keys. One possible implementation would be to use those four arrow keys for directional navigation. For accessibility and user convenience, user agents should allow configuration of which keys on a keyboard are used for directional navigation.
<IP_ADDRESS>. Example: positioned buttons
Here is an example of buttons positioned in a diamond shape whose directional focus navigation is set in such a way to navigate the focus clockwise (or counter-clockwise) around the diamond shape when the user chooses to navigate directionally.
button { position:absolute }
button#b1 {
top:0; left:50%;
nav-right:#b2; nav-left:#b4;
nav-down:#b2; nav-up:#b4;
}
button#b2 {
top:50%; left:100%;
nav-right:#b3; nav-left:#b1;
nav-down:#b3; nav-up:#b1;
}
button#b3 {
top:100%; left:50%;
nav-right:#b4; nav-left:#b2;
nav-down:#b4; nav-up:#b2;
}
button#b4 {
top:50%; left:0;
nav-right:#b1; nav-left:#b3;
nav-down:#b1; nav-up:#b3;
}
Whatever markup sequence the buttons may have (which is not specified in this example) is irrelevant in this case because they are positioned, and yet, it is still important to ensure focus navigation behaviors which relate reasonably to the specified layout.
<IP_ADDRESS>. Example: moving focus to inside a frame
Moving the focus to an element in a specific frame requires both the element’s id and the frame’s name.
This example shows how to make navigating left from the button with id "foo" move the focus to the element with id "bar" within the frame named "sidebar".
button#foo { nav-left: #bar "sidebar"; }
6.3.2. Obsolete: the ime-mode property
"ime-mode" is a property somewhat implemented in some browsers, that is problematic and officially obsoleted by this specification.
There is documentation of non-interoperability of these implementations.
User agents should not support the ime-mode property.
Authors must not use the ime-mode property.
Users may use the ime-mode property only for repair use-cases where they have to work around bad sites and legacy implementations, e.g. with a user style sheet rule like:
This example CSS may be placed into a user style sheet file to force password input fields to behave in a default manner.
This specification deliberately does not attempt to document the functionality of legacy ime-mode implementations nor what they specifically support because it does not make sense to pursue or recommend any such path.
- The global
lang
attribute - The
inputmode
,pattern
, andtype
attributes of the input element
Appendix A. Acknowledgments
This appendix is informative.
This specification was edited and written for the most part by Tantek Çelik from 1999 to the present, first while representing Microsoft, then as an invited expert, and most recently while representing Mozilla.
Thanks to Florian Rivoal, working on this specification on behalf of Bloomberg, for his recent work documenting issues from www-style emails, proposing resolutions & changes, and in particular for researching & writing greatly improved details for the box-sizing property.
Thanks to feedback and contributions from Rossen Atanassov, Tab Atkins, L. David Baron, Bert Bos, Matthew Brealey, Rick Byers, Ada Chan, James Craig, Michael Cooper, Axel Dahmen, Michael Day, Micah Dubinko, Elika E., Steve Falkenburg, Andrew Fedoniouk, Al Gilman, Ian Hickson, Bjoern Hoehrmann, Alan Hogan, David Hyatt, Richard Ishida, Sho Kuwamoto, Yves Lafon, Stuart Langridge, Susan Lesch, Peter Linss, Kang-Hao Lu, Masayuki Nakano, Mats Palmgren, Brad Pettit, François Remy, Andrey Rybka, Simon Sapin, Alexander Savenkov, Sebastian Schnitzenbaumer, Lea Verou, Etan Wexler, David Woolley, Frank Yan, Boris Zbarsky, and Domel.
Appendix B. Changes
This appendix is informative.
In general this draft contains editorial/grammatical/spelling corrections, and a few new informative examples. This appendix describes functional changes from the Working Draft (WD) of 17 Jan 2012 that were made to reflect implementer adoption (or lack thereof), as well as implementer innovations, and feedback from the general public. In particular, changes since the previous draft fall into one of three categories:
- Minor refinements to features based on implementation experience.
- Dropping features that were not implemented, or were insufficiently implemented to exit CR.
- Adding a small number of new but already interoperably implemented features.
List of substantial changes since the 2015-05-19 Working Draft
- Strengthened accessibility related messages about use and abuse of the outline property
- Changed the handling of unsupported cursor values to standard CSS error handling.
- Dropped the padding-box value of the box-sizing property due to no implementation interest from UA vendors.
- Clarified that the cursor property affects the shape of the cursor when within the border edge
- Added 'resize: both' to the default HTML stylesheet for textarea elements
List of substantial changes since the 2015-04-09 Working Draft
- box-sizing effects on CSS 2.1 width and height computations specified much more explicitly.
- cursor image formats normatively required.
- caret-color is inherited and animatable.
- New informative appendix on Considerations for Security and Privacy.
List of substantial changes since the 2015-03-10 Working Draft
Only editorial changes were made.
List of substantial changes since the 2015-02-24 Working Draft
- ::value and ::choices pseudo-elements have been dropped due to insufficient implementer interest. As they were published in a previous CR draft, they may be re-added in a future level if implementers show interest and intent to implement.
List of substantial changes since the 2012-02-17 Last Call Working Draft
- ::value pseudo-element. Added detail about which properties apply to the ::value pseudo-element.
- text-overflow property - added <string> value and 2 values option, both explicitly at risk.
- nav-up, nav-right, nav-down, and nav-left properties removed from the "at risk" list.
- Dropped the nav-index property due to lack of implementation interest.
- cursor values "grab" and "grabbing" added per multiple interoperable implementations.
- Numerous UI selectors moved to Selectors4 and CSS Pseudo module.
- add caret-color property, but at risk.
- ime-mode explicitly obsoleted.
- outline-offset define negative values.
- Dropped the icon property.
- Dropped the icon value of the content property.
- XForms-only pseudo-elements dropped.
Appendix C. Considerations for Security and Privacy
This appendix is informative.
The W3C TAG is developing a Self-Review Questionnaire: Security and Privacy for editors of specifications to informatively answer.
Per the Questions to Consider
- Does this specification deal with personally-identifiable information?
No.
- Does this specification deal with high-value data?
No.
- Does this specification introduce new state for an origin that persists across browsing sessions?
No.
- Does this specification expose persistent, cross-origin state to the web?
No.
- Does this specification expose any other data to an origin that it doesn’t currently have access to?
No.
- Does this specification enable new script execution/loading mechanisms?
Yes. The cursor property accepts <image> values which may include URLs to be loaded.
- Does this specification allow an origin access to a user’s location?
No.
- Does this specification allow an origin access to sensors on a user’s device?
Yes. The directional focus navigation properties indirectly allow access to the device’s keyboard navigation input mechanism such as arrow keys.
- Does this specification allow an origin access to aspects of a user’s local computing environment?
No.
- Does this specification allow an origin access to other devices?
No.
- Does this specification allow an origin some measure of control over a user agent’s native UI?
Yes. The cursor and caret-color properties enable the page to change the display of the cursor and text insertion caret of the user agent’s native UI. In addition the outline-style property’s auto value (and thus outline shorthand) enable the page to potentially display a native focused element outline presentation around any element.
- Does this specification expose temporary identifiers to the web?
No.
- Does this specification distinguish between behavior in first-party and third-party contexts?
No.
- How should this specification work in the context of a user agent’s "incognito" mode?
No differently.
- Does this specification persist data to a user’s local device?
No.
- Does this specification have a "Security Considerations" and "Privacy Considerations" section?
Yes.
- Does this specification allow downgrading default security characteristics?
No.
Appendix D. Default style sheet additions for HTML
This appendix is informative.
Potential additions to the base style sheet to express HTML form controls, and a few dynamic presentation attributes:
:enabled:focus { outline: 2px inset; } button, input[type=button], input[type=reset], input[type=submit], input[type=checkbox], input[type=radio], textarea, input, input[type=text], input[type=hidden], input[type=password], input[type=image] { display: inline-block; white-space: nowrap; } button { /* white space handling of BUTTON tags in particular */ white-space:normal; } input[type=reset]:lang(en) { /* default content of HTML input type=reset button, per language */ content: "Reset"; } input[type=submit]:lang(en) { /* default content of HTML input type=submit button, per language */ content: "Submit"; } /* UAs should use language-specific Reset/Submit rules for others. */ input[type=button], input[type=reset][value], input[type=submit][value] { /* text content/labels of HTML "input" buttons */ content: attr(value); } textarea { /* white space handling of TEXTAREA tags in particular */ white-space:pre-wrap; resize: both; } input[type=hidden] { /* appearance of the HTML hidden text field in particular */ display: none; } input[type=image] { display: inline-block; content: attr(src,url); border: none; } select[size] { /* HTML4/XHTML1 <select> w/ size more than 1 - appearance of list */ display: inline-block; height: attr(size,em); } select,select[size=1] { /* HTML4/XHTML1 <select> without size, or size=1 - popup-menu */ display: inline-block; height: 1em; overflow: hidden; } select[size]:active { /* active HTML <select> w/ size more than 1 - appearance of active list */ display: inline-block; } optgroup,option { display: block; white-space: nowrap; } optgroup[label],option[label] { content: attr(label); } option[selected]::before { display: inline; content: check; } /* Though FRAME resizing is not directly addressed by this specification, the following rules may provide an approximation of reasonable behavior. */ /* frame { resize:both } frame[noresize] { resize:none } */
Appendix E: Test Suite
This appendix is informative.
There is a partial test suite written according to the CSS Test Suite Documentation and following the CSS2.1 Test Case Authoring Guidelines. The test suite shall allow user agents to verify their basic conformance to the specification. This test suite does not pretend to be exhaustive and does not cover all possible combinations of user interface related features. These tests will be made available from the CSS Test Suites home page.


Eel Boilerplate it's a prebuilt project to help you start with your Eel development
I chose a set of components I like, to help you start building fast:


A stunning and robust app showcase.
Good Business
A stunning and robust app showcase.
Good Business
The worlds leading Lorem ipsum dolor sit amet coectrur adispsigind elit se ddoAmaizing functionality
Amaizing functionality
The worlds leading Lorem ipsum dolor sit amet coectrur adispsigind elit se ddoOptimized for performance
The worlds leading Lorem ipsum dolor sit amet coectrur adispsigind elit se ddo| Free goodies | Features | Free | Premium | |
|---|---|---|---|---|
| Acces 35 mill songs on demand and ad-free | Listen on web ios android | |||
| Store up to 50.000 songs | ||||
| get recomandations based on your taste | ||||
| Over 50 free premium tools | Curated radio for anithing you want to hear | |||
| Acces 35 mill songs on demand and ad-free | ||||
| Ad-free unintrerupted listenning | ||||
| 5GB of free storage space | Download music to play when yuo are not connected | |||
| Skip as many songs as you want |


I was never really into hard drugs before my first encounter with Twack, a local term for meth. I had experimented with a few others, but none had given me the complete and instant euphoria I encountered with Twack.
It was by chance that I came across my first line. I was going through my mom's purse looking for pot when I found a small bag with some off-whitish powder in it and a straw. I took some for future experimentation. A few weeks later I was home alone one night and decided to hop on the drug train. I set out 2 lines at around 6pm, both about 2' in length, and 1/4' in width, a quarter of that would have been more than enough.
The sting in my nose was awful. It felt as if I had inhaled glass. Tears poured out of the eye on the side I put it in. The drip was disgusting and very bitter. Then the head rush hit me. It was incredible. I felt absolutely euphoric. I have always been a shy and self conscious person, but meth took all that away. I was up for 18 hours after that, cleaning meticulously, writing pages and pages in my journal, and fixing myself in the mirror. It took away all desire to eat or drink anything, the perfect diet. The crash was gruesome, like a combination of bad hangover and influenza, but as soon as that was over I was craving more.
I have been tweaking as regularly as possible since then. It takes me more and more to get up, the high seems less and less high and is shorter each time. I have trouble with picking at my skin, I'll wake up after a tweak with big red open scabs all over my face. I also distroy my jaw and tongue. I can scarcely taste foods I used to enjoy as I wreck so many taste buds. My jaw gets very sore from clenching. Once during a final, I chewed the inside of my cheek so raw that it got infected and I had to see a doctor.
I have lost a lot of weight since my first tweak, but I gain it all back as soon as I stop doing it. It may make me feel fantastic for a few hours, but compared to how crappy I feel and how unhealthy it makes me the rest of the time, I would regret ever starting.
Experience Reports are the writings and opinions of the individual authors who submit them.
Some of the activities described are dangerous and/or illegal and none are recommended by Erowid.


@* * Copyright 2023 HM Revenue & Customs * * Licensed under the Apache License, Version 2.0 (the "License"); * you may not use this file except in compliance with the License. * You may obtain a copy of the License at * * http://www.apache.org/licenses/LICENSE-2.0 * * Unless required by applicable law or agreed to in writing, software * distributed under the License is distributed on an "AS IS" BASIS, * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. * See the License for the specific language governing permissions and * limitations under the License. *@ @import cats.syntax.order._ @import play.api.i18n.Messages @import uk.gov.hmrc.cgtpropertydisposalsfrontend.controllers.accounts.homepage @import uk.gov.hmrc.cgtpropertydisposalsfrontend.models.finance.{AmountInPence, MoneyUtils} @import uk.gov.hmrc.govukfrontend.views.html.components._ @import uk.gov.hmrc.cgtpropertydisposalsfrontend.views.ViewHelpers @this(viewHelpers: ViewHelpers) @(totalLeftToPay: AmountInPence, hasRecentlyAmendedReturn : Boolean)(implicit messages: Messages) @numberClass = @{ if(totalLeftToPay.inPounds() > 999999999 || hasRecentlyAmendedReturn) "govuk-heading-s" else if (totalLeftToPay.inPounds() > 99999999) "govuk-heading-l" else "govuk-heading-xl" } @pendingClass = @{ if(hasRecentlyAmendedReturn) " pending" else "" }
@messages("account.totalLeftToPay.payments")


spotify-web-api-kotlin
/
com.adamratzman.spotify.models
/
CountryCode
CountryCode
(common, js, jvm)
typealias
CountryCode
=
Market
Deprecated:
Country enum has been updated to preserve consistency with Spotify documentation


Check Out And Build Community Edition
Installing Git
The source code of IntelliJ IDEA Community Edition is stored in a Git repository. Therefore, in order to check out the sources, you need to have Git installed. We recommend using the msys git distribution on Windows and git-osx-installer on Mac.
Checking Out the Code
You can check out the code either by using IntelliJ IDEA or from the command line.
Checking out from IntelliJ IDEA:
- Select VCS | Checkout from Version Control | Git from the main menu
- In the Git Repository URL field, enter
git://git.jetbrains.org/idea/community.git
Checking out from the command line:
Please execute the following command:
git clone --depth 1 git://git.jetbrains.org/idea/community.git idea
The master branch currently contains the code for the most recent development version of IntelliJ IDEA. Source code of older releases of IntelliJ IDEA can be found in the following branches:
| IntelliJ Product version | Branch name/number |
|---|---|
| 15.0.x | 143 |
| 14.1.x | 141 |
| 14.0.x | 139 |
| 13.1.x | 135 |
| 13.0.x | 133 |
| 12.0.x | 123 |
| 11.1.x | 117 |
| 11.0.x | nika |
| 10.5.x | xena |
| 10.0.x | x0x |
| 9.x | maia |
The source code of stable releases of IntelliJ IDEA Community Edition is also available as a tarball:
- IntelliJ IDEA Community Edition 15.0.1
- IntelliJ IDEA Community Edition 14.1.4
- IntelliJ IDEA Community Edition 13.1.6
- IntelliJ IDEA Community Edition 13.0.4
- IntelliJ IDEA Community Edition 12.1.6
- IntelliJ IDEA Community Edition 12.0.4
- IntelliJ IDEA Community Edition 11.1.4
- IntelliJ IDEA Community Edition 11.0.2
- IntelliJ IDEA Community Edition 10.5.4
- IntelliJ IDEA Community Edition 10.0.3
- IntelliJ IDEA Community Edition 9.0.4
Forking on GitHub
As an alternative to checking out the official repository, you can fork the GitHub mirror of the IntelliJ Platform source code, make changes in your own fork, and send us a pull request.
The GitHub mirror can be found at https://github.com/JetBrains/intellij-community.
Building and Running from the IDE
To develop plugins and applications on the IntelliJ Platform, you can use either IntelliJ IDEA Community Edition or IntelliJ IDEA Ultimate.
Building and running the code
-
Make sure you have the Groovy plugin enabled by going to Settings | Plugins and enabling Groovy plugin checkbox.
Parts of IntelliJ IDEA are written in Groovy, and you will get compilation errors if you don’t have the plugin enabled.
-
Make sure you have the UI Designer plugin enabled. Most of the IntelliJ IDEA platform UI is built using the UI Designer, and the version you build will not run correctly if you don’t have the plugin enabled.
- Open the directory with the source code as a directory-based project.
-
Configure a Java SDK named IDEA jdk (case sensitive), pointing to an installation of JDK 1.8
-
Add
lib\\tools.jar
from the JDK installation directory to the classpath of IDEA JDK - Use Build | Make Project to build the code.
-
To run the code, use the IDEA shared run configuration provided by the project.
Building and Running from the Command Line
To build the distribution archive of IntelliJ IDEA Community Edition, execute the build.xml Ant build script in the root directory of the source code.
The results of the build execution can be found at out/artifacts.


Color-Practice
Photoshop & Wacom Tablet
Human Poses
Photoshop & Mouse
Illustration for my book
Ipad Pro & Apple Pen
Character for my book
Photoshop & Wacom Tablet
Eye Study
Pencil and Paper
Illustration for my book
Ipad Pro & Apple Pen (App: Sketchbook)
Landscape for Fun
Ink and Watercolorpaper
Character for my Book
Ipad Pro & Apple Pen (App: Sketchbook)
Animal & Structure Pratcice
Photoshop & Wacom Tablet
Raven Sketch
Ipad Pro & Finger
Building for my book
Chameleon Pens & Paper
Random Demom
Photoshop & Wacom Tablet
Zurück


Arsenal told to spend £40million to replace Unai Emery with Brendan Rodgers
Arsenal chief Emery is under growing pressure from fans at the Emirates after a disappointing start to the season, but has been publicly backed by the club
by Alex Richards, https://www.facebook.com/AARichards/Arsenal have been told to spend £40million to snare Brendan Rodgers and replace Unai Emery with the Leicester City boss.
The Gunners inconsistent start to the season continued on Saturday with a 2-0 defeat to Rodgers’ high-flying Foxes.
Jamie Vardy and James Maddison scored second-half goals to send Leicester second in the Premier League.
By contrast, pressure continues to mount on Emery, with Arsenal having won just four of their first 12 league fixtures this term and already sitting eight points behind the top four.
Gunners chiefs have backed the Spaniard, insisting that they "firmly believe Unai is the right man for the job.
But ex-Arsenal star Paul Merson retains doubts over Emery’s long-term future, and says Arsenal should go all out to land Rodgers as his replacement.
“I think he's [Rodgers] one of the best in the business,” Merson told Sky Sports.
“If I was Arsenal, I would have been ringing Leicester up and saying, 'how much do you want?'.
“If you're going to pay £72million for a winger [Pepe] that hasn't played in the Premier League and has played in the French league, I would pay £40million for him tomorrow morning.
“I would say Arsenal [would be a good fit for Rodgers]. Arsenal or Tottenham . I wouldn't get rid of Pochettino, don't get me wrong, I think he's different class.
"I think them two teams will be looking at him.
“For me, if you're going to bring Brendan Rodgers in and what he's done with the teams he has been at like Swansea, Celtic, Liverpool and now Leicester, you give him a six-year plan and let him do what he wants to do.
"He improves players.”
Merson’s declaration comes after the Arsenal hierarchy sent an impassioned message to staff about his future.
They told staff: “We are as disappointed as everyone else with both our results and performances at this stage of the season. We share the frustration with our fans, Unai, players and all our staff as they are not at the level we want or expect.
“Things need to improve to meet our objectives for the season, and we firmly believe Unai is the right man for the job, together with the backroom team we have in place. We are all working intensively behind the scenes to turn things around and are confident we will.
“We never take our fantastic support for granted. We hope we can all stick together and get behind the team in this challenging period, as together we are stronger.”


Born in Missouri and raised in Arizona, I have spent many of my adult years looking for my tribe, I feel I finally have found them in the field of progamming! My first time experiencing the joys (and headaches) of coding was when I was eleven years old. At that time my school was working with HTML 3.2, doing styling in-line. I continued playing around with HTML and CSS for many years and now I'm back at it with the LPS UPenn Coding Bootcamp! I served in the U.S. Army for five years straight out of high school, learning much about the world during that time. After that chapter had closed, I began searching for my next adventure in past passions. I started self educating in C++ and evetually Python to see if it was an activity I still enjoyed. The excitment was still present with every new hurdle passed and knowledge gained. I am thrilled to be a part of this challenging curriculum with the wonderful staff that is here to help transform me into a full-fledged web developer!


Update ServiceAccount of pod template resources.
Possible resources (case insensitive) can be:
replicationcontroller (rc), deployment (deploy), daemonset (ds), job, replicaset (rs), statefulset
Aliases:
serviceaccount, sa
Examples:
# Set Deployment nginx-deployment's ServiceAccount to serviceaccount1
kubectl set serviceaccount deployment nginx-deployment serviceaccount1
# Print the result (in yaml format) of updated nginx deployment with serviceaccount from local file, without hitting apiserver
kubectl set sa -f nginx-deployment.yaml serviceaccount1 --local --dry-run=client -o yaml
kubectl set serviceaccount (-f FILENAME | TYPE NAME) SERVICE_ACCOUNT [options]
Use "kubectl options" for a list of global command-line options (applies to all commands).


Agrela House / spaceworkers
- Curated by Matheus Pereira
- about 16 hours
- version="1.0" encoding="UTF-8"? Architects: spaceworkers
- AreaArea of this architecture projectArea: 365.0 m2
- version="1.0" encoding="UTF-8"?YearCompletion year of this architecture project Year: 2018
- version="1.0" encoding="UTF-8"?PhotographsPhotographs: Fernando Guerra | FG+SG
- Architects in Charge Henrique Marques, Rui Dinis
- Project Team Marco Santos, Marta Silva, Mónica Pacheco, Tiago Maciel
- Furniture Design Bairro Design
- Finance Director Carla Duarte - cfo
- Engineering Simetria Vertical
- Start of project 2014
More Specs Less Specs
Text description provided by the architects. A house for books. This challenge started with a premise from the client: space for many books. Immediately, our imaginary guided us to the many classical renaissance libraries, with sliding stairs that reach the book mountain. That was the motto of the intervention: a high space capable of generate the composition and hierarchize interior spaces.
The ideia was growing and the volumetric experience led to the functional differentiation of the interior spaces, crating a roof as a restless mass with different heights. The roof also figures itself in a fifth facade and influences the idealization of the other ones.
Suddenly we had created a dense, heavy, monolithic cover roof that needed to be subverted, giving an idea of levitating mass that is slightly lying on light wood and glass. The roof seems to crush the users, reminding them of their own scale as humans and the ancestral importance of the shelter.
The time - important architectural component - is also an essential agent of the composition. The built elements - specially in concrete - seek to register the passage of time through it formwork texture.
This formwork, similar to the roof variations, assumes ups and downs, protrusions and recesses, allowing it to keep the time with the representation of the shadows during the different hours of the day, giving also a dramatic appearance to the facades
As the time passes the textured concrete will naturally age and will be more integrated in the rural surroundings. The same will happen to the wood base, which the older it gets the more magnificence will become, enriching the house


"Internet? You mean the thing we click to search our favorite dish recipe or look up videos of the 'Corgi Flop'?"
Yes! We often take the amazing powers of the Internet for granted because -- let's face it -- it's been available for us without any cost! I know nobody likes a know-it-all... but allow me to show you in steps how the Internet really works. Wouldn't hurt, right?
Step 1.
This is the part you're probably the most familiar with. It's simply when you type the desired website's url (i.e. github.com) into your brower.
Step 2.
One of the key components of the Internet is called the hardware. It includes everything from the cables to a modem and/or router. A modem or a router allows you to travel to another network around the world. Firewalls in your browser act as a security guard that permits or prohibits incoming/outcoming data.
Step 3.
Now... SOMETHING's got to be storing all these information we find on the web, right? Unsurprisingly, there are machines called the servers that store information. When your query reaches the ISP (Internet Service Provider), one of many servers called a DNS Server (Domain Name Server) translates the text domain name (github.com) into the numerically specific IP address.
Step 4.
With the identified IP address, your browser will now get ready to take you to the unique location on the World Wide Web using a special language called the hypertext transfer protocol (http).
Step 5.
The brower travels through the cloud, which consists of all the other ISPs and home/business networks. It is a network of networks, so in essence the cloud is the Internet.
Step 6.
A successful connection between you and the desired website is established.
Step 7.
Your brower finally brings back the data and information from the website to your computer. The rate of retrieval is usually faster than the rate of establishment.
There you have it, folks. This is how the Internet works. Beautiful!


ESP32 Main configuration
Home
Applications
Mesh
Modbus
MQTT
Network
Local WiFi
User Login
About us
Modbus Configuration
Link node
LogoMeter RS485 Output
Pulse Output
Standard RS485 Output
Select your meter application.
Baud Rate
La tasa de baudios del medidor
Conversion factor [imp/kWh]
Initial Energy
Number of initial energy of your meter screen
Slave ID
Range 1 to 255
Submit


Do you think your friends should know?
Thank you for adding a video, we will let you know when it's live.
That username has already been claimed.
Capture the best parts of online videos.
We are proud to announce that Bubbl is spending the summer with Media Camp and the Entrepreneur’s Roundtable Accelerator.
Stay tuned, big things coming…


This demo uses the
Basis C++ transcoder (compiled to Javascript using Emscripten) to transcode a .basis Universal Texture Video file directly to GPU texture data, with no intermediate recompression step.
.basis universal GPU texture files can be quickly transcoded directly to any other GPU texture format with little to no quality loss.
Thanks to Evan Parker for providing
webgl-texture-utils and this test bed.
NOTE: Your browser does not support DXT, so using RGB565
for the texture below. To get DXT, try Chrome 19+
(beta channel as of 2012-04-20; graphics card DXT support also required).


TATTOOING IS REALLY HARD
Today there are more than 15,000 tattoo parlors in the U.S., compared to roughly 500 professional tattoo artists operating in 1960. But while the industry is booming, it’s difficult to get your foot in the door. The first step is to get an apprenticeship under a reputable artist who will teach you all they know, but that can take years of persistence. “I just now have an apprentice and he’s been bugging me about it for three years,” says Chad Leever, a tattoo artist in Indiana. His best tip for landing an apprenticeship? “Hang out, get to know us, get tattooed, but even then it will probably still be no. It’s really tough".
THEY PRACTICE ON THEMSELVES
It may be years before an artist-in-training gets to wield a tattoo gun. When they finally get their first shot at inking some real human skin, it’s often attached to their own body. “I just had my apprentice tattoo himself,” Leever says. “It was terrible tattoo. It turned out horrible. He messed it up and he’ll learn from that but now things will make more sense the next time he does it".
A GOOD ARTIST WILL SAY NO
Whatever your age or employment status, there are some tattoos artists just won’t do, either because it’s not their specialty or they know it won’t look good or heal well. The professionals will be honest about this. Small, intricate designs might not age well, and finger tattoos won’t last. A good artist will warn you about these potential complications and maybe even refuse the work.
 “Being an apprentice, we can make you do anything,” Leever says. During his own apprenticeship, Leever had to get his navel pierced.  “It was this colorful rainbow thing and I had to leave it in for 10 days and show every person who came into the shop. It was horrible".


noisegen
noisegen samples
> island
> clouds
> clouds (alt)
> water
> frost
> blood
Algorithm: Simplex
Octaves: 9
Persistence: 0.52
Scale: 0.025
Palette:
Algorithm: Perlin
Octaves: 6
Persistence: 0.6
Scale: 0.02
Palette:
Algorithm: Perlin
Octaves: 6
Persistence: 0.6
Scale: 0.02
Palette:
Algorithm: Worley
Region Dimensions: 128
N Closest Points: 1
Density Mean: 3
Density Deviations: 1
Palette:
Algorithm: Worley
Region Dimensions: 64
N Closest Points: 5
Density Mean: 1
Density Deviations: 1
Palette:
Algorithm: Worley
Region Dimensions: 128
N Closest Points: 1
Density Mean: 5
Density Deviations: 1
Palette:


I am experienced in .NET frameworks development of ASP.net Web and Mobile (Android and ios) Applications. collaborative thinking to further the overall value proposition.
Involved in the Consumer Digital Service Dashboards development and to maintaining the Edm based application
Involved in the FETCH development the maintaining logistics based application
Involved in the development of the block chain technology based application on the ethereum wallets and hyper ledgers.
Involved in the development and integrating the chatbot with the existing projects, Slack and the Messenger social applications.
Involved in the development and maintaining client based applications. In Logistics and Social Application of the Mobile Android and ios application.
Involved in the development and maintaining client based applications. This application for the Web and Mobile based application.IOT Device Integration with this project using Microsoft azure and c#.
CGPA: 8.0
Percentage : 84%
Percentage : 82%
Apart from being a web developer, I would like to play Cricket and carom board games.
When forced indoors, I follow a number of sci-fi and fantasy genre movies and television shows, I am an aspiring chef, and I spend a large amount of my free time exploring the latest technology advancements in the front-end web development world.


By the mid-14th century, medieval Swansea had reached its maximum size and remained like this until the 1800s. This does not mean that the urban landscape stopped changing, however. New buildings were constructed after 1300, such as the town walls and gates, New Castle, and St David’s Hospital. These were all significant building projects, showing that there was money in Swansea at this time to fund these works, as well as a desire by the lord and the townspeople to use them to show off the status of the town to traders and visitors. St David’s Hospital is one of Swansea’s most important medieval landmarks. Now a public house, it is a good place to end the tour of the development of Swansea and reflect on how much the town has changed through the centuries.