eBayUI Core
Collection of Marko widgets; considered to be the core building blocks for all eBay components, pages & apps.
Requirements
Note: eBayUI Core components utilize Marko flags and, therefore, require <lasso-page/> to be added to any page which will have core components.
Note: @ebay/skin/global and @ebay/skin/marketsans are required to be loaded by your app for all modules to load correctly.
Note: In order for spread attributes to work properly, [email protected] at least is required
Browser Policy
All components are developed and tested cross-browser using BrowserStack, in accordance with our official eBay Browser Policy.
Accessibility (A11Y)
We take accessibility very seriously. Very seriously indeed. Therefore, all components are built in accordance to the eBay MIND Patterns. These patterns, in turn, build on from the specifications provided by the WAI-ARIA Authoring Practices.
Components are built in a layered, progressively enhanced fashion, utilizing the following resources:
Each layer does its bit to enforce and enhance accessibility. We consider this level of support to be one of our chief selling points, and we hope you do too!
Components
ebay-3d-viewerebay-badgeebay-breadcrumbsebay-buttonebay-carouselebay-checkboxebay-comboboxebay-cta-buttonebay-detailsebay-drawer-dialogebay-eekebay-fake-menuebay-fake-menu-buttonebay-fake-tabsebay-filterebay-filter-menuebay-filter-menu-buttonebay-fullscreen-dialogebay-iconebay-infotipebay-inline-noticeebay-lightbox-dialogebay-listbox-buttonebay-menuebay-menu-buttonebay-page-noticeebay-paginationebay-panel-dialogebay-progress-barebay-progress-stepperebay-radioebay-section-noticeebay-section-titleebay-selectebay-signalebay-snackbar-dialogebay-split-buttonebay-star-rating-selectebay-switchebay-tabsebay-textboxebay-toastebay-tooltipebay-tourtipebay-video
Getting Started
The eBayUI core components are available as the @ebay/ebayui-core package on NPM.
Use npm or yarn to add the package dependency to your project:
npm add @ebay/ebayui-coreUpgrading to the latest versions
See the upgrade guide for more information
Custom Tags
Once the package dependency is added, the eBay customs tags are now available for use in your Marko templates. For example, to use an ebay-menu component:
template.marko
<ebay-menu text="Sort" type="radio">
<@item>Price</@item>
<@item>Time</@item>
<@item>Distance</@item>
</ebay-menu>Attributes
Attributes provide initial state for a component. We can see that the menu has text and type attributes:
template.marko
<ebay-menu text="Sort" type="radio">
<@item>Price</@item>
<@item>Time</@item>
<@item>Distance</@item>
</ebay-menu>Passing new attributes to an ebayui component will always reset it's internal state. If you want to persist this state yourself, events are exposed which allow you to synchronize the state into your own components, for example:
class {
onCreate() {
this.state = {
dialogIsOpen: false
}
}
handleDialogClose() {
this.state.dialogIsOpen = false;
}
handleDialogOpen() {
this.state.dialogIsOpen = true;
}
}
<ebay-lightbox-dialog
open=state.dialogIsOpen
on-open('handleDialogOpen')
on-close('handleDialogClose')>
...
</ebay-lightbox-dialog>Pass-Through Attributes
HTML attributes can be used on any component, and they will be passed through to the most prominent tag of the component. The most prominent tag is usually the root or form control, but individual components will note if it varies for specific cases.
Example of static usage:
<ebay-button id="my-button"/>For using pass-through attributes dynamically, they should be sent through the html-attributes attribute:
$ const myAttributes = { id: 'my-button' };
<ebay-button html-attributes=myAttributes/>Static and dynamic pass-through attributes can be used simultaneously (html-attributes takes precedence in conflicts):
$ const myAttributes = { id: 'my-button' };
<ebay-button html-attributes=myAttributes type="submit"/>Events
Events can also be handled using Marko syntax:
template.marko
<ebay-menu text="Sort" type="radio" on-change("onMenuChange")>
<@item>Price</@item>
<@item>Time</@item>
<@item>Distance</@item>
</ebay-menu>Releases & Milestones
For upcoming roadmap and release history, please refer to our releases and milestones pages.
Versioning
The ebayui-core package follows strict Semantic Versioning.
Given a version number MAJOR.MINOR.PATCH:
- MAJOR version is incremented when we make incompatible API changes
- MINOR version is incremented when we add functionality in a backwards-compatible manner
- PATCH version is incremented when we make backwards-compatible bug fixes.
Deprecations
Deprecations will be communicated via release notes, so please ensure that you read those carefully. In general, expect any deprecated feature to be removed in the next major version. However, in some cases we may wait a while longer.
Issues
Please use our issues page to ask questions, report issues or submit feature requests.
To help track your issue, our admins will assign it with one or more coloured labels:
- Black: Issue Type (e.g. bug, question, test case)
- White: Resolution (e.g. wont fix, invalid, duplicate)
- Gray: Status (e.g. backlog, in progress, help wanted)
- Red: Blocker (e.g. dependency, discussion, design)
- Green: Module (e.g. button, radio, dialog)
- Blue: Aspect (e.g. build, documentation, website)
- Yellow: Semver Guidance (e.g. breaking change, backwards compatible)
- Purple: Sprint (e.g. sprint 1, sprint 2, etc)
Contributing
Looking to contribute to eBay UI? Please visit our contributing page for more information.
License
Copyright (c) 2018 eBay Inc.
Use of this source code is governed by a MIT-style license that can be found in the LICENSE file or at https://opensource.org/licenses/MIT.
USE OF SOME COMPONENTS REQUIRES A SEPARATE, NON-OPEN-SOURCE LICENSE FROM THIRD PARTIES
The data visualization components and the charting components of the eBayUI library are designed to use one or more HighCharts® software products. HighCharts® is a registered trademark of HighSoft AS. HighSoft AS is not affiliated with Ebay. Ebay provides no warranties of any kind (e.g., of merchantability, fitness for a particular purpose, and noninfringement), whether express or implied, with respect to the HighCharts® software products that the data visualization components and the charting components are designed to use.
COMMERCIAL USE OF HIGHCHARTS® SOFTWARE PRODUCTS REQUIRES A PAID LICENSE PROVIDED BY HIGHSOFT AS. While many components of the eBayUI library are licensed under the MIT License, the HighCharts® software products which the data visualization components and charting components of the EbayUI library are designed to use are NOT licensed under the MIT License or any other open source license. Rights pertaining to HighCharts® software products (e.g., including, but not limited to, rights to use, install, distribute, publish, merge, duplicate, and modify) are governed by the terms of one or more proprietary license agreements that are available online at http://www.highcharts.com or by the terms of custom license agreements that HighSoft AS may negotiate with its customers at its own discretion. While HighSoft AS may choose to license HighCharts® software products for non-commercial use at no cost, IT IS THE RESPONSIBILITY OF ANY PARTY THAT WISHES TO USE HIGHCHARTS® SOFTWARE PRODUCTS TO VERIFY THE TERMS OF SUCH A LICENSE WITH HIGHSOFT AS. NOTWITHSTANDING ANY PROVISION OF THIS LICENSE, PARTIES WHO ARE NOT LICENSED BY HIGHSOFT AS (OR ITS SUCCESSORS OR ASSIGNS) TO USE HIGHCHARTS® SOFTWARE PRODUCTS ARE NOT LICENSED TO USE THE DATA VISUALIZATION COMPONENTS AND THE CHARTING COMPONENTS OF THE EBAYUI LIBRARY.
This notice shall be included in all copies or substantial portions of the Software.